{"version":"2.1.290","anchor":"mcp-tool-results-with-structuredcontent-now-route-non-text-b","canonical_anchor":"mcp-tool-results-with-structuredcontent-now-route-non-text-b","heading":"Rich MCP tool results are converted in a different order","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/mcp-tool-results-with-structuredcontent-now-route-non-text-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Rich MCP tool results are converted in a different order\n\nMCP tool results that carry structured data now go through a new conversion step first, with the old handling kept as a fallback\n\n**Unclear.** What the new first conversion step does differently from the old handling is not clear.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Some return results with both a `structuredContent` part, which is machine-readable data, and a list of content blocks such as text or images.\n\nClaude Code now tries a new conversion step on those content blocks first. If that does not apply, it falls back to the old handling: the non-text blocks, followed by a text block. Non-text blocks are converted before the structured text is used.\n\nTwo smaller changes come with this:\n\n- Tools that come from MCP servers now record which plugin supplied them.\n\n- Tools supplied through the SDK, the kit that lets other programs drive Claude Code, now pass along the details of the inputs they accept.\n\n**Why**\n\nThis may change how results that mix structured data, images and text are shown to Claude.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}