Skip to main content
Glama

Topolograph

resolve_route

Read-onlyIdempotent

Resolve the path a router would take to a destination, one row per routing decision -- hands off between static/BGP/IGP/LSP whenever one of them overrides the plain SPF path.

Input fields: graph_time (str): The IGP graph to resolve against start_node (str): Router ID the resolution starts from destination (str): Router ID or free-typed prefix rt (str, optional), vrf (str, optional), rd (str, optional): three ways to name one VPN; rt is the only one that identifies it across PEs evidence (str): pre_policy, post_policy, loc_rib (default), or fib -- what the answer rests on when start_node's table is not observed directly with_lsps (bool): Let MPLS TE LSPs override the plain IGP path (default: true) changed_edge_costs (dict, optional): igraph edge id -> new metric, for what-if cost planning

Equivalent to POST /graph/{graph_time}/route-resolution/{start_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>",
      "start_node": "<start_node>",
      "destination": "<destination>"
    },
    "name": "resolve_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
rdNo
rtNo
vrfNo
evidenceNoloc_rib
with_lspsNo
graph_timeYes
start_nodeYes
destinationYes
changed_edge_costsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, and the description adds real context beyond that: the per-decision row granularity, the protocol hand-off behavior, the default LSP override, and the what-if edge-cost simulation. It also maps the tool to a concrete REST endpoint, which helps an agent reason about semantics. It stops short of describing result size or latency characteristics, which the output schema partly covers.

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?

The opening sentence is front-loaded with the core behavior, and the input-field list is well organized with type hints and defaults. The structured list is somewhat long but each line adds information not present in the schema, so little is wasted.

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 nine-parameter tool with zero schema description coverage, the description is unusually complete, covering every parameter plus the REST equivalent, and an output schema exists so return values need not be explained. Minor gaps remain: no indication of expected identifier formats (router ID syntax, graph_time format) or where valid values come from.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so: it documents all nine parameters, including the subtle rt/vrf/rd distinction ('rt is the only one that identifies it across PEs') and the enumerated evidence levels (pre_policy, post_policy, loc_rib, fib) that the schema itself lacks. changed_edge_costs is described as an igraph-edge-id-to-metric map, adding format meaning absent from the schema.

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?

Uses a specific verb and resource ('Resolve the path a router would take to a destination') and adds scope detail: one row per routing decision, including static/BGP/IGP/LSP hand-offs that override the plain SPF path. This meaningfully distinguishes it from plain path tools like get_shortest_path, though it never names an alternative tool explicitly.

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

Usage Guidelines3/5

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

Usage context is implied through parameters: 'evidence' explains what the answer rests on when start_node's table is not observed directly, and 'changed_edge_costs' is scoped to what-if cost planning. However, there is no explicit statement of when to choose this over siblings such as get_shortest_path, get_path_tree, or search_bgp_routes, and no when-not 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.