Skip to main content
Glama

Topolograph

get_path_tree

Read-onlyIdempotent

The shortest-path tree rooted at one router, equal-cost paths included.

Input fields: graph_time (str): The graph time node (str): Node name, hostname or IS-IS System ID direction (str, optional): "out" for paths from the node (default), "in" for paths to it at (str, optional): ISO 8601 moment; a watcher graph is shown with the events up to it

Output fields: dict with result {root, direction}, nodes and edges (the links of the tree).

Equivalent to GET /graph/{graph_time}/path/{node}.

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": {
      "graph_time": "<graph_time>",
      "node": "<node>"
    },
    "name": "get_path_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo
nodeYes
directionNoout
graph_timeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavior: equal-cost paths are included in the tree, and when `at` is supplied the watcher graph shows only events up to that moment. It also sketches the return shape (root, direction, nodes, 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 purpose is front-loaded in one sentence, then parameters and return values are listed in a scannable structure. Nothing is padded, and the schema-style repetition of parameter names is justified by the 0% schema coverage.

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

Completeness4/5

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

For a 4-parameter read-only graph query with an output schema present, the definition covers purpose, all parameters, and the return shape. The main residual gap is the vague definition of `graph_time` and the absence of any note on graph availability or size of the returned tree.

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?

With 0% schema description coverage, the description carries the full burden and mostly succeeds: `node` accepts a name, hostname, or IS-IS System ID; `direction` has meaningful out/in semantics and a stated default; `at` is an ISO 8601 moment that truncates watcher events. Only `graph_time` is weakly defined with the circular gloss 'The graph time'.

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 states a specific verb+resource: it returns the shortest-path tree rooted at one router, with equal-cost paths included, and names the backing endpoint GET /graph/{graph_time}/path/{node}. It does not explicitly differentiate itself from siblings like get_shortest_path or get_cspf_path, so an agent must infer the distinction from the word 'tree'.

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 guidance relative to alternatives; the closest siblings (get_shortest_path, get_cspf_path) are never mentioned. The direction field hints at from-vs-to usage, but that is parameter semantics rather than tool-selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.