Skip to main content
Glama

Topolograph

get_routes

Read-onlyIdempotent

Answers "where is MAC/IP X", VRF/VNI contents, and hosts behind a leaf: routes of the BGP epochs bound to this graph (the latest of every source), current state by default.

Input fields: graph_time (str): The IGP graph time, or the name of your OSPF/IS-IS watcher (Enterprise): the snapshot alive at at (or now) is read and named in the answer's graph_time router_id (str, optional): Scope to one router's resolved RIB view; omit for the whole bound epoch vni (int, optional): EVPN L2VNI vrf (str, optional): VRF name, resolved to its RDs across the bound epoch's own routers rt (str, optional): Any of the route's route targets rd (str, optional): Route distinguisher vtep (str, optional): EVPN originating IP or next-hop prefix (str, optional): CIDR is an exact match; an address returns every covering route, longest prefix first mac (str, optional): EVPN exact match at (str, optional): Point in time (ISO 8601) instead of current state page (int): Page number, 1-indexed (default: 1) per_page (int): Items per page (default: 50)

Output fields: dict with items (route rows, current state carries the winning nexthop) and pagination. An EVPN row's evpn.route_type is the EVPN route type: RT-1 Ethernet A-D, RT-2 MAC/IP, RT-3 IMET, RT-4 Ethernet Segment, RT-5 IP prefix.

Equivalent to GET /graph/{graph_time}/routes or GET /graph/{graph_time}/node/{router_id}/routes.

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>"
    },
    "name": "get_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo
rdNo
rtNo
macNo
vniNo
vrfNo
pageNo
vtepNo
prefixNo
per_pageNo
router_idNo
graph_timeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world, so the safety profile is covered. The description goes further by explaining that results come from the epochs bound to the graph, that the latest of every source is used, that current state is the default, and that current-state rows carry the winning nexthop. It does not mention rate limits or result-size limits, but the behavioral picture is otherwise rich.

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 definition is front-loaded with the answer-first sentence, then cleanly sectioned into Input fields and Output fields, and each parameter line earns its place by adding meaning. It is on the long side and the indented param listing is dense, but there is no filler prose or repetition of the tool name.

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?

For a 12-parameter read tool the description covers scope, defaults, per-parameter semantics, pagination, the shape of the return value, the EVPN route_type decoding, and the equivalent REST endpoints. An agent has everything needed to call it correctly and interpret the response without opening the schema.

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 it delivers: every one of the 12 parameters is documented with real semantics rather than a name echo. Especially valuable are router_id (resolved RIB view vs whole epoch), vrf (resolved to its RDs across the epoch's own routers), prefix (CIDR as exact match vs address returning covering routes longest-prefix-first), and mac (EVPN exact match).

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 opening sentence states a concrete verb and resource (returns routes of the BGP epochs bound to this graph) plus the three question shapes it answers: where-is-MAC/IP, VRF/VNI contents, and hosts behind a leaf. That is far more specific than a restatement of the name. It stops short of distinguishing itself from close siblings such as search_bgp_routes, get_bgp_route_state, or resolve_route.

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 is implied through the question-based framing ("where is MAC/IP X", "hosts behind a leaf") and the note that current state is returned by default, with `at` for historical. However, no explicit when-to-use/when-not-to-use guidance or named alternative appears, so an agent must infer the boundary against sibling route tools on its own.

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.