Update dsl-reference.md

Author: amin-nikanjam

dsl-reference.md

@@ -539,17 +539,17 @@ The [MCP Call](#mcp-call) enables workflows to interact with MCP servers that ar
 | Name | Type | Required | Description|
 |:--|:---:|:---:|:---|
 | method | `string` | `yes` | The MCP JSON-RPC method to send.<br>*Supported values are: `initialize`, `notifications/initialized`, `prompts/list`, `prompts/get`, `notifications/prompts/list_changed`, `resources/list`, `resources/read`, `resources/templates/list`, `notifications/resources/list_changed`, `tools/list`, `tools/call`, `notifications/tools/list_changed`, `logging/setLevel`, and `notifications/message`* |
-| server | `string`\|[`endpoint`](#endpoint) | `yes` | An URI or an object that describes the MCP server to call.<br>|
-| parameters | `map` <br> `string` | `no` | The parameters for the MCP RPC method. For the `initialize` method, runtimes must set the `protocolVersion` parameter to the used version.<br>*Can be an object or a runtime expression.* |
+| server | `string`\|[`endpoint`](#endpoint) | `yes` | An URI, an object (for HTTP) or a filename (for STDIO) that describes the MCP server to call.<br>|
+| parameters | `map` <br> `string` | `no` | The parameters for the MCP RPC method. For the `initialize` method, runtimes must set the `protocolVersion` parameter to the used version. Runtimes must implement the MCP specification version of 2025-06-18. <br>*Can be an object or a runtime expression.* |
 
 > [!NOTE]
 > On success the output is the JSON-RPC result. On failure runtimes must raise an error with type [https://serverlessworkflow.io/spec/1.0.0/errors/runtime](https://github.com/serverlessworkflow/specification/blob/main/dsl-reference.md#standard-error-types).
 >
-> This call only supports MCP over HTTP transport mechanism and not STDIO (communication over standard in and standard out).
+> This call supports MCP over both HTTP and STDIO (communication over standard in and standard out) transport mechanisms.
 
 ###### Examples
 
-This example shows an initialization phase as the first interaction between MCP client and server. The client sends its supported version, capabilities, and implementation informationin the initialize request. The server MUST respond with its own capabilities and information including the supported version.
+This example shows an initialization phase as the first interaction between MCP client and server. The client sends its supported version, capabilities, and implementation information in the initialize request. The server MUST respond with its own capabilities and information including the supported version.
 
 ```yaml
 document: