Skip to main content
Glama

Get one distributed trace

get_trace
Read-only

One trace (app → backend → dependencies) as a tree: names, services, start offsets, durations, HTTP status and errors, plus the error events linked to it. Take the trace_id from an event or from search_traces. Use it to see where the time went or what failed first. Long traces page with next_cursor.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "trace_id": "<trace_id>"
    },
    "name": "get_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoSpans (default 100)
cursorNonext_cursor from the last answer
trace_idYes32-character hex W3C trace id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "next_cursor from the last answer",
      +  "maxLength": 20,
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Spans (default 100)",
      +  "maximum": 300,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds useful behavior beyond that by disclosing the tree-shaped return contents and that long traces page via next_cursor. It does not mention any limits on trace retention or failure modes when the trace id is unknown, but the operationally important behavior is stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the payload structure, then provenance, then purpose, then pagination. No filler or restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the burden of describing returns — and it does so specifically (status, durations, errors, linked error events). Combined with the paging note, an agent has everything needed to call and interpret this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is already 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining where trace_id comes from (an event or search_traces) and by tying cursor/paging to long traces. The 'limit' parameter's span-vs-trace semantics are left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource — one distributed trace — and enumerates what the tree contains (names, services, start offsets, durations, HTTP status, errors, linked error events). The singular 'One trace' plus the arrow notation (app → backend → dependencies) distinguishes it clearly from the sibling search_traces, which returns many.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete routing and provenance: take the trace_id from an event or from search_traces, and use this to see where the time went or what failed first. That is enough to pick the tool correctly, but there is no explicit statement of when not to use it (e.g. when you only have a service name and must search first).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources