Skip to main content
Glama

traces_operations

List a service's operations and endpoints from Jaeger to identify which trace targets you can investigate.

Instructions

List operations/endpoints for a service. 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": {
      "service": "<service>"
    },
    "name": "traces_operations"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYesService name
lookbackNoTime window (used by some providers)1h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses little beyond naming the backend (Jaeger). It does not state that the operation is read-only, what the returned operations look like, whether results are paginated or complete, or how provider differences (hinted at by lookback being 'used by some providers') affect behavior.

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

Conciseness4/5

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

Two short sentences with the purpose front-loaded and no filler. The backend note is useful context rather than padding, though the definition is arguably too terse rather than too long.

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?

For a simple two-parameter read tool with full schema coverage this is minimally adequate, but with no annotations and no output schema the description should at least characterize the returned operation list and error behavior for an unknown service.

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%, so both parameters are already documented in the schema, and the description adds no further semantics such as accepted service naming conventions or whether lookback is silently ignored by Jaeger. Baseline 3 applies when the schema does the heavy lifting.

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?

Uses a specific verb ('List') and a concrete resource ('operations/endpoints for a service'), which is clearly distinct from sibling tools like traces_search or traces_services. It stops short of explicitly contrasting with those siblings, but the resource is unambiguous.

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?

There is no statement of when to use this versus traces_search or trace_get, no prerequisite that a service name must come from traces_services first, and no note on what happens for an unknown service. Usage is only implied by the required 'service' parameter.

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