Skip to main content
Glama

traces_dependencies

Compute a service dependency graph from Jaeger traces to show which services call which within a configurable lookback window.

Instructions

Service dependency graph — which services call which. 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_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
lookbackNoTime window to compute dependencies (e.g. "1h", "1d")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 provided, so the description carries the full burden. It discloses the backend (Jaeger) and that dependencies are computed over a time window, but says nothing about what the graph contains (nodes/edges), whether it requires traces to be present, how aggregation works, or whether the result is bounded. For a graph-derivation tool that must be distilled from trace data, this is thin.

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 before the backend attribution. Every clause is relevant, though the terseness leaves obvious behavioral gaps rather than over-explaining.

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

Completeness2/5

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

There is no output schema and no annotations, so the description should convey what the returned dependency graph looks like and how the lookback shapes it. It instead only states the resource and backend, leaving an agent to guess at return structure and scope.

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 single optional lookback parameter already documents its format and default in the schema, so the baseline is 3. The description adds no syntax, default, or time-window semantics beyond that, so it neither compensates nor regresses.

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 names a specific resource and defines it: "Service dependency graph — which services call which." That clause distinguishes it from a plain service listing such as traces_services, so an agent knows this tool returns call relationships rather than a flat inventory. It stops short of naming or contrasting any sibling directly, which keeps it from a 5.

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 explicit when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives such as traces_services or topology-oriented siblings. Usage is only inferable from the phrase "dependency graph" itself.

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