{"version":"2.1.315","anchor":"mcp-strip-trailing-xml-tags-flag-and-claude-docs-wake-wrappe","canonical_anchor":"mcp-strip-trailing-xml-tags-flag-and-claude-docs-wake-wrappe","heading":"Claude docs MCP tools get extra handling and one result-size rule is narrower","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/mcp-strip-trailing-xml-tags-flag-and-claude-docs-wake-wrappe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Claude docs MCP tools get extra handling and one result-size rule is narrower\n\nTools from a Claude docs MCP server are now wrapped in an extra step, and one condition for treating a tool result's size specially no longer applies\n\n**Unclear.** It is not clear which servers count as a Claude docs server or what the extra step does for them.\n\n**What**\n\nMCP servers are programs that give Claude extra tools. Two things changed in how Claude Code prepares these tools:\n\n- Claude docs tools: tools from a server Claude Code identifies as a Claude docs server now go through an extra step when they are created, which relates to how those tools wake.\n\n- Result size: one of the conditions that marked a tool's results as carrying a size note, a tool keeping its text inline, no longer counts.\n\nThe setting that strips trailing XML tags from MCP results is unchanged and falls back to off.\n\n**Why**\n\nThis affects how results from some MCP tools are handled and how tools from a Claude docs server start up.\n\n- Flag `tengu_mcp_strip_trailing_xml_tags`: Not enough to say (read for one account on one subscription tier against v2.1.315; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}