{"version":"2.1.288","anchor":"mcp-oversized-or-unparseable-responses-now-give-a-specific-e","canonical_anchor":"mcp-oversized-or-unparseable-responses-now-give-a-specific-e","heading":"Clearer error when an MCP tool's response is too big or the connection drops","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/mcp-oversized-or-unparseable-responses-now-give-a-specific-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Clearer error when an MCP tool's response is too big or the connection drops\n\nFailed MCP tool calls now say if the response passed the size limit or the connection closed, and warn the tool may already have run\n\n**What**\n\nMCP servers are separate programs that give Claude extra tools. When a call to one of their tools fails because the reply was too large or could not be read, the error is now specific. It says either that the response passed the size limit, given in MB, or that the connection closed. It also says the server may already have run the tool, so this call got no result.\n\nBefore, the error was generic.\n\n**Why**\n\nIf the tool may already have run, retrying it could do the same thing twice. The new message tells you that before you retry.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}