{"version":"2.1.288","anchor":"mcp-tool-calls-too-large-and-closed-connection-errors-rai","canonical_anchor":"mcp-tool-calls-too-large-and-closed-connection-errors-rai","heading":"MCP tool calls report oversized results and closed connections as their own errors","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/mcp-tool-calls-too-large-and-closed-connection-errors-rai","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### MCP tool calls report oversized results and closed connections as their own errors\n\nAn MCP tool result that is too large, or a connection that closes for a recognised reason, now raises its own error instead of looking like an expired session\n\n**Unclear.** Which close reasons count as recognised is not stated.\n\n**What**\n\nMCP servers are add-on programs that give Claude extra tools. Their tools can fail in two ways that Claude Code now reports separately:\n\n- **Result too large:** Claude Code raises a specific error, and that error includes the size limit.\n\n- **Connection closed for a recognised reason:** Claude Code raises a different specific error.\n\nBefore, both were handled as if the server's session had expired.\n\n**Why**\n\nClaude Code no longer reconnects to the server again and again just because a result was too big.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}