{"version":"2.1.265","anchor":"wire-tool-input-consistency-check-telemetry-now-includes-too","canonical_anchor":"wire-tool-input-consistency-check-telemetry-now-includes-too","heading":"Wire tool input consistency-check telemetry now includes tool name and MCP flag","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/wire-tool-input-consistency-check-telemetry-now-includes-too","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Wire tool input consistency-check telemetry now includes tool name and MCP flag\n\nTool input consistency-check telemetry now records the tool's name and whether it's an MCP tool\n\n**What**\n\nWhen Claude Code detects an inconsistency in a tool's recorded input (via the `tether_wire_tool_input` telemetry event), the event now also includes the tool's name (`toolName`) and whether it came from an MCP server (`isMcp`), an external tool provider connected via the Model Context Protocol.\n\n**Why**\n\nThis gives more context for diagnosing which specific tool, and whether an MCP-provided one, triggered an inconsistent recorded input, making it easier to track down the source of such issues.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}