{"version":"2.1.299","anchor":"mcp-tool-calls-get-per-call-timing-marks-and-per-server-desc","canonical_anchor":"mcp-tool-calls-get-per-call-timing-marks-and-per-server-desc","heading":"MCP tools get per-server description limits, timing marks and server ids","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/mcp-tool-calls-get-per-call-timing-marks-and-per-server-desc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### MCP tools get per-server description limits, timing marks and server ids\n\nMCP tool descriptions are limited per server, tool calls mark timing phases, and tool display data carries server_id, server_id_stamp and tool_name\n\n**Unclear.** It is not clear which servers get which description limit.\n\n**What**\n\nMCP (Model Context Protocol) servers supply extra tools to Claude Code. Several parts of how these tools are listed and shown changed.\n\n- Tool listing now works out a separate `maxDescriptionLength` and `maxLoadedDescriptionLength` for each server, instead of one global limit, and passes them into each tool. The count of over-long descriptions is now measured against the per-server limit.\n\n- Tool listing also adds a `serverIdStamp`.\n\n- The display data for each tool call now carries `server_id` (the claude.ai connector id), `server_id_stamp` (an `X-MCP-Server-ID` stamp for dynamic http entries) and the bare `tool_name`. Before, it held only `display_name`, `server_display_name` and `icon_url`.\n\n- MCP tool calls accept a new `timing` option and mark 'approval', 'own' and 'external' phases. WebFetch and ToolSearch mark timing segments too. This measures where time is spent inside Claude Code.\n\nThe stock WebFetch description captured under this release is unchanged.\n\n**Why**\n\nHow much of a tool's description is cut off can now differ from one server to another, which changes what Claude sees. Programs that show tool calls can use the new ids to display a call as belonging to its connector.\n\n- Flag `tengu_mcp_strip_trailing_xml_tags`: Not enough to say (read for one account on one subscription tier against v2.1.299; 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: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}