Skip to main content
Glama

system_topology

Retrieve live service dependency topology with health overlays from Jaeger and the application API to map relationships and identify unhealthy dependencies.

Instructions

Get the live service dependency topology with health overlays from Jaeger and the application API.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

B3.4/5.0
Behavior3/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. It usefully discloses that the data is live, aggregated from two sources (Jaeger and the application API), and that health status is overlaid on the topology. It does not state whether the call is read-only (only implied by 'Get'), how fresh or cached the data is, expected latency, or any permission requirements.

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?

A single front-loaded sentence with no filler. The scope ('live', 'dependency topology', 'health overlays') arrives immediately, and every phrase adds information.

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 no-parameter read tool this covers what the result conceptually is, but with no output schema present the description leaves the return structure unstated (nodes, edges, health fields, depth of graph). Adding one clause on the shape of the response would make it fully self-sufficient.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description's mention of sources is context rather than parameter meaning.

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 specific verb ('Get') and resource ('live service dependency topology with health overlays'), plus the underlying sources (Jaeger and the application API). An agent can tell this is a topology/dependency view rather than a raw trace or metric query, though it never names the closest sibling (traces_dependencies) to draw the line explicitly.

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. The word 'live' implies a current-state snapshot rather than historical analysis, but nothing tells the agent whether to prefer this over traces_dependencies or system_health, and no prerequisites are stated.

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