{"version":"2.1.300","anchor":"tool-and-llm-telemetry-spans-gain-gen-ai-attributes","canonical_anchor":"tool-and-llm-telemetry-spans-gain-gen-ai-attributes","heading":"Tool traces now carry standard GenAI attributes for OpenTelemetry","tier":"notice","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/tool-and-llm-telemetry-spans-gain-gen-ai-attributes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Tool traces now carry standard GenAI attributes for OpenTelemetry\n\nTraces of tool use now include standard GenAI fields such as the tool name, and the MCP server name for MCP tools\n\n**What**\n\nOpenTelemetry is a standard way to send traces, records of what a program did, to monitoring tools. When tracing is on, the record for each tool call now includes:\n\n- `gen_ai.operation.name` set to `execute_tool`\n\n- `gen_ai.tool.name`, the tool's name\n\n- `anthropic.mcp.server.name`, for tools that come from an MCP server (an add-on that supplies tools)\n\nBefore, the record held only the tool name in Claude Code's own fields. A failed tool result now also reports whether it was interrupted.\n\n**Why**\n\nMonitoring tools that understand the standard GenAI attributes can now group and filter Claude Code's tool calls without custom mapping.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}