{"version":"2.1.317","anchor":"tool-call-telemetry-records-mcp-server-state-and-transport","canonical_anchor":"tool-call-telemetry-records-mcp-server-state-and-transport","heading":"Usage data records how a tool's server was doing when a call waited","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/tool-call-telemetry-records-mcp-server-state-and-transport","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Usage data records how a tool's server was doing when a call waited\n\nWhen a tool call waits for an MCP server's tool, Claude Code's usage data now records that server's state and connection type\n\n**What**\n\nMCP servers are separate programs that give Claude extra tools. Sometimes a tool call has to wait because the server providing the tool is not ready yet. Claude Code's usage data for a tool call now records three more details:\n\n- the server's state while the call waited\n\n- the server's state when the wait began\n\n- the kind of connection used to reach the server\n\n**Why**\n\nThis gives Anthropic a view of how often tools from MCP servers that connect late hold up a call. It does not change what you see.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}