{"version":"2.1.301","anchor":"turn-end-failure-message-and-mcp-call-oversize-result-messag","canonical_anchor":"turn-end-failure-message-and-mcp-call-oversize-result-messag","heading":"Claude is told more clearly why a turn did not end or an MCP result went missing","tier":"notice","area":"Messages","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/turn-end-failure-message-and-mcp-call-oversize-result-messag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Claude is told more clearly why a turn did not end or an MCP result went missing\n\nClaude now gets explicit notes when a failed tool call stops a turn from ending and when an oversized MCP result is dropped\n\n**What**\n\nA tool call is a single action Claude takes, such as reading a file or running a command. A turn is one round of Claude's work before it hands control back to you. Claude Code now sends Claude two new messages for unusual situations:\n\n- A turn that did not end: Claude asked to end its turn, but another tool call in the same message failed. Claude is told the turn did not end and that it should deal with the failure first.\n\n- An oversized MCP result: MCP (Model Context Protocol) lets Claude Code use tools from outside servers. When such a call's result was meant to be kept from Claude and was too large, Claude is told the result went over the size limit and nothing came back.\n\n**Why**\n\nIn both cases Claude now gets a plain explanation instead of being left to guess. It should handle a failed action before stopping, and it should not assume a large MCP result arrived.\n\n- Area: Messages\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}