tool-intercept-logger

To log tool calls with OTEL metrics, you need a tool-intercept-logger that captures pre- and post-execution data for each tool, storing OTEL-compatible spans in SQLite to generate observable records for debugging and performance analysis.

Auditing token costs for tool calls requires generating a session summary that calculates call counts, success rates, token usage, and costs, highlighting top-cost tools to provide actionable insights for cost auditing.

Yes, you can monitor specific MCP integrations using scope control, which allows logging all tools, filtering by namespace, or targeting specific named tools to validate new MCP integrations and verify tool selection.

Session summary observability works by recording every tool execution in OTEL-compatible format, then calculating call metrics like success rates and token usage to produce a summarized report for handoff or ongoing analysis.

No dependencies are required to capture OTEL-compatible spans in SQLite; the tool-intercept-logger operates independently to store pre- and post-execution data and produce actionable telemetry records.

Tool monitoring matters for cost auditing and debugging because tool calls are invisible by default, making it difficult to analyze performance, verify token costs, and debug unexpected tool selections without structured logging and session summaries.