You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`ctx.mcpReq.elicitInput(params, options?)`| Elicit user input (form or URL) |`server.elicitInput(...)` from within handler |
417
417
|`ctx.mcpReq.requestSampling(params, options?)`| Request LLM sampling from client |`server.createMessage(...)` from within handler |
418
418
419
-
## 11. Schema parameter removed from `request()`, `send()`, and `callTool()`
419
+
## 11. Schema parameter on `request()` / `callTool()` is optional; removed from `send()`
420
420
421
-
`Protocol.request()`, `BaseContext.mcpReq.send()`, and `Client.callTool()`no longer take a Zod result schema argument. The SDK resolves the schema internally from the method name.
421
+
`Protocol.request()`and `Client.callTool()`still accept a Zod result schema as the second argument (the v1 form), but it is optional for spec methods — the SDK resolves the schema internally from the method name. `BaseContext.mcpReq.send()` no longer takes a schema.
422
422
423
423
```typescript
424
424
// v1: schema required
@@ -427,20 +427,20 @@ const result = await client.request({ method: 'tools/call', params: { ... } }, C
|`client.callTool(params, CompatibilityCallToolResultSchema)`|unchanged (schema ignored), or `client.callTool(params)`|
443
+
|`client.callTool(params, schema, options)`|unchanged, or `client.callTool(params, options)`|
444
444
445
445
Remove unused schema imports: `CallToolResultSchema`, `CompatibilityCallToolResultSchema`, `ElicitResultSchema`, `CreateMessageResultSchema`, etc., when they were only used in `request()`/`send()`/`callTool()` calls.
### `Protocol.request()`, `ctx.mcpReq.send()`, and `Client.callTool()` schema parameter is now optional
400
+
### `Protocol.request()` and `Client.callTool()` schema parameter is now optional
401
401
402
-
The public `Protocol.request()`, `BaseContext.mcpReq.send()`, and `Client.callTool()` methods still accept a result schema argument, but for spec methods it is optional — the SDK resolves the correct schema internally from the method name. You no longer need to import result schemas
403
-
like `CallToolResultSchema` or `ElicitResultSchema` when making requests.
402
+
The public `Protocol.request()` and `Client.callTool()` methods still accept a result schema argument, but for spec methods it is optional — the SDK resolves the correct schema internally from the method name. You no longer need to import result schemas
403
+
like `CallToolResultSchema` or `ElicitResultSchema` when making requests. (`BaseContext.mcpReq.send()` no longer accepts a schema; drop it.)
| Task interactive server | Task-based execution with interactive server→client requests. |[`src/simpleTaskInteractive.ts`](src/simpleTaskInteractive.ts)|
39
39
| Hono Streamable HTTP server | Streamable HTTP server built with Hono instead of Express. |[`src/honoWebStandardStreamableHttp.ts`](src/honoWebStandardStreamableHttp.ts)|
40
40
| SSE polling demo server | Legacy SSE server intended for polling demos. |[`src/ssePollingExample.ts`](src/ssePollingExample.ts)|
41
-
| Custom (non-standard) methods server | Registers `acme/*` custom request handlers and sends custom notifications.|[`src/customMethodExample.ts`](src/customMethodExample.ts)|
41
+
| Custom (non-standard) methods server | Registers `acme/*` custom request + notification handlers and emits custom progress notifications. |[`src/customMethodExample.ts`](src/customMethodExample.ts)|
0 commit comments