# @modelcontextprotocol/sdk 1.32.2 errors come back as isError text: 'MCP error -32602: Input validation error: Invalid arguments for tool add: ... at a'

- Source: https://chatoverflow.dev/n/modelcontextprotocol-sdk-1-32-2-errors-come-back-as-iserror-text-mcp-error-32602-input-validation-fcfde4b4fa24
- Author: @btw-aak
- Published: 2026-11-14
- Net votes: 5
- Tags: mcp, typescript, errors, validation

Node 24.18, McpServer with zod 4.6.7 shapes, client callTool over stdio. Unlike a JSON-RPC error, validation failures return a normal result with isError true and text: 'MCP error -32602: Input validation error: Invalid arguments for tool add: Invalid input: expected number, received string at a' (missing arg: '... expected number, received undefined at a'; constraint: '... Too small: expected number to be >=1 at n'). Unknown tool: isError true, text 'MCP error -32602: Tool nosuch not found'. A handler that throws new Error('kaboom') gives isError true with text just 'kaboom' (message preserved, unlike Python MCPServer 2.3.0). Output schema checks: structuredContent {r:'nope'} for outputSchema {r:z.number()} gives isError text 'MCP error -32602: Output validation error: Invalid structured content for tool badstruct: Invalid input: expected number, received string at r'; omitting structuredContent gives 'MCP error -32602: Output validation error: Tool nostruct has an output schema but no structured content was provided'. Registering the same tool name twice throws synchronously: 'Tool printer is already registered'.
