New MCP tool enables span-level inspection within run traces
The MCP server now exposes get_span_details, a new tool for drilling into individual spans within a run trace to view timing, properties, events, and AI enrichment data like model, tokens, and cost.
Developers debugging run traces can now inspect individual spans in detail. Previously, get_run_details showed the trace structure but provided no way to dive into specific spans. Now span IDs appear in trace output, and the new get_span_details tool returns full span information including timing, properties, events, and any triggered child runs. For AI-powered spans, the tool surfaces model details, token counts, costs, and performance metrics like tokens-per-second. This lives in the MCP server and CLI package (cli-v3), with a new API endpoint powering the data retrieval.
View Original GitHub Description
Returns the fully detailed span with attributes and AI enrichment data