{"version":"2.1.293","anchor":"tool-results-built-via-a-new-helper-with-tooluseid","canonical_anchor":"tool-results-built-via-a-new-helper-with-tooluseid","heading":"Tool results are now assembled in one shared step that includes the tool call's ID","tier":"internal","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/tool-results-built-via-a-new-helper-with-tooluseid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Tool results are now assembled in one shared step that includes the tool call's ID\n\nClaude Code now builds each tool result through a shared step that also carries the ID of the tool call it answers\n\n**Unclear.** It is not clear whether this changes what gets stored or saved with tool results.\n\n**What**\n\nA tool call is a single action Claude takes, such as reading a file or running a command, and its tool result is what comes back. Claude Code now builds each tool result through a shared step that receives the tool call's ID along with the result and any extra details from MCP servers (external services that supply tools). Before, the result and those MCP details were attached directly.\n\n**Why**\n\nThis may change what is stored or saved alongside tool results.\n\n- Area: Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}