Skip to main content
Glama

traces_services

Lists services known to the Jaeger traces backend, helping you identify applications emitting telemetry; optionally scope results with a lookback time window.

Instructions

List services known to the traces backend. Backend: Jaeger.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "traces_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 behavioral burden. It usefully names the backend ('Jaeger'), which hints at provider-specific behavior, but says nothing about whether the call is read-only, whether the 'lookback' window is honored for this provider, ordering, or the shape of the returned services.

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, front-loaded with the purpose and followed by the backend qualifier; nothing is padded. Slightly terse for the amount of behavioral information an annotation-free tool needs.

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 one-optional-parameter read tool with no output schema, the description is adequate to call it, but it leaves gaps: whether lookback applies to Jaeger, and what a returned service entry contains (name only, tags?) are unanswered.

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?

With 100% schema description coverage on a single optional 'lookback' parameter, the schema already documents the input. The description adds no meaning about lookback and notably does not clarify that the schema itself warns lookback is only used by some providers, so no value is added beyond structured data.

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?

States a concrete verb ('List') and resource ('services known to the traces backend'), which is specific enough for an agent to know it enumerates service names rather than spans or operations. It does not explicitly contrast with siblings like traces_operations or traces_dependencies, so differentiation is only implicit.

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 when-to-use or when-not-to-use guidance and no mention of alternatives such as traces_operations for drilling into a single service. The discovery intent is only inferable from the verb 'List'.

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