agent-trace-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRACE_FILE | No | Path to the JSONL trace file. Defaults to `~/.agent-trace-mcp/traces.jsonl`. | ~/.agent-trace-mcp/traces.jsonl |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| trace_recordA | Append one agent or MCP tool span. Reuse run_id for every span in the same user turn. |
| trace_list_runsB | List recent agent runs with span counts, errors, and token totals. |
| trace_get_runB | Return every span for one run id. |
| trace_failed_toolsC | Return recent spans that failed. |
| trace_token_costA | Sum input and output tokens. Omit run_id to sum the whole file. |
| trace_slowest_toolsB | Return the slowest spans by latency_ms. |
| trace_statusA | Show the JSONL path and how many spans are stored. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a distinct purpose: recording, listing runs, retrieving a run, filtering failures, computing token costs, finding slowest tools, and checking status. No overlaps or ambiguity.
All tools follow the consistent pattern of 'trace_' prefix plus a descriptive verb or noun phrase, using snake_case throughout. This makes the tool set predictable and easy to navigate.
With 7 tools, the server is well-scoped for tracing functionality—covering recording, querying, and analysis without excess or deficiency.
The surface covers core tracing needs: record, list, get, filter failures, cost, performance, and status. Minor gaps like clearing or deleting runs exist but are not critical for typical usage.