{"version":"2.1.290","anchor":"mcp-never-answered-tool-call-message","canonical_anchor":"mcp-never-answered-tool-call-message","heading":"Clearer error when an MCP tool call never gets an answer","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/mcp-never-answered-tool-call-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Clearer error when an MCP tool call never gets an answer\n\nIf an MCP tool call's response ends before any answer arrives, Claude is told the outcome is unknown and to check before retrying\n\n**What**\n\nMCP servers (Model Context Protocol servers) are add-ons that give Claude extra tools. Sometimes the connection carrying a tool's response closes before any answer arrives. Claude now receives an error saying the outcome is unknown. It explains that the call may have finished, may still be running, or may never have started, and asks Claude to check what the call did before repeating it.\n\n**Why**\n\nThis discourages Claude from simply running the call again. That matters for actions that should not happen twice, such as sending a message or creating a record.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}