Skip to main content
Glama

jaeger_get_dependencies

Read-onlyIdempotent

Retrieve service dependency graph showing parent-child call counts to map service topology and verify connections.

Instructions

Retrieve the service-to-service call graph from Jaeger.

Wraps GET /api/dependencies. Returns directed edges (parent → child) with call_count — the number of spans where parent called child in the lookback window.

Use this to understand service topology, find high fan-out services, or verify that a new service is connected as expected.

Examples: - Use when: "What services does order-service call?" → check edges where parent='order-service'. - Use when: "Map the full service dependency graph for the last 7 days" → lookback_hours=168. - Use when: "Which services are called most frequently?" → sort edges by call_count descending. - Don't use when: You want detailed span timings (use jaeger_search_traces + jaeger_get_trace instead). - Don't use when: You need real-time data — Jaeger's dependency graph is aggregated and may lag by minutes.

Returns: dict with end_ts_us / lookback_hours / edge_count / edges (list of {parent, child, call_count}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_tsNoEnd timestamp in microseconds since Unix epoch UTC (optional). Defaults to now. Example: 1713400000000000.
lookback_hoursNoNumber of hours to look back from end_ts (1-720, default 24).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_ts_usYes
lookback_hoursYes
edge_countYes
edgesYes
Behavior5/5

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

Annotations already provide readOnlyHint and idempotentHint; the description adds that the dependency graph is aggregated and may lag by minutes, and that it wraps GET /api/dependencies. It also discloses the return structure including fields like end_ts_us, lookback_hours, edge_count, and edges.

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?

The description is concise and well-structured: brief intro, clear bullet points for use cases, explicit don't-use cases, and a return format summary. Every sentence adds value without redundancy.

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?

Given the tool's low complexity (2 parameters, all optional), the description covers all necessary aspects: purpose, usage guidelines, behavioral caveats, and return format. It is fully adequate for an agent to select and invoke the tool correctly.

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 100% with both parameters well-documented. The description adds value by providing concrete examples of parameter usage (e.g., lookback_hours=168 for 7 days), but the schema alone already explains the parameters adequately, so this is slightly above baseline.

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 clearly states the verb 'Retrieve' and specific resource 'service-to-service call graph from Jaeger'. It distinguishes from sibling tools by providing explicit use cases and when not to use it, e.g., 'Don't use when: You want detailed span timings (use jaeger_search_traces + jaeger_get_trace instead)'.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool with concrete examples (e.g., 'What services does order-service call?', 'Map the full service dependency graph for the last 7 days'), and when not to use it with alternatives, such as for real-time data or detailed span timings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mshegolev/jaeger-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server