Skip to main content
Glama

trace_get

Retrieve complete trace details by trace ID from Jaeger to inspect spans, timing, and service dependencies.

Instructions

Get full trace detail by ID. Backend: Jaeger.

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": "trace_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
trace_idYesTrace ID (hex string)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the result is 'full trace detail' and that the backend is Jaeger, but says nothing about authorization needs, error behavior for missing/invalid IDs, rate limits, or what 'full' includes.

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?

Two short sentences with zero waste. The core action is front-loaded, and the backend note is compact and useful.

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

Completeness3/5

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

This is a simple single-parameter retrieval tool, so the description need not be long. However, with no annotations and no output schema, it could do more to clarify return contents or failure behavior.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already documents trace_id as a hex string, so the baseline is 3. The description reinforces that the parameter is an ID but adds no format or validation meaning beyond the schema.

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

Purpose4/5

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

The description states a specific verb and resource: 'Get full trace detail by ID.' The 'by ID' phrasing helps distinguish it from search-style siblings such as traces_search, though it does not explicitly name an alternative.

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

Usage Guidelines2/5

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

Usage is only implied by 'by ID' — the agent can infer this is for when a trace ID is already known. There is no explicit guidance on when to use this versus traces_search or verify_trace, nor any prerequisite about how to obtain the trace ID.

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