Skip to main content
Glama

Topolograph

list_vpns

Read-onlyIdempotent

Answers "which VNI/VRF exists on which leaf": the fabric-wide VPN/VRF/VNI inventory of the BGP epochs bound to this graph, or one router's own view.

Input fields: graph_time (str): The IGP graph time router_id (str, optional): Scope to one router's resolved RIB view; omit for the fabric-wide list page (int): Page number, 1-indexed (default: 1) per_page (int): Items per page (default: 25)

Output fields: VpnsResponse: dict with items (VpnRow: name, route_targets, route_distinguishers, vni, l3vni, prefix_count), pagination, and, router-scoped only, evidence/can_build_path/assumptions.

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

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

Input Schema

NameRequiredDescriptionDefault
pageNo
per_pageNo
router_idNo
graph_timeYes

Output Schema

NameRequiredDescriptionDefault
itemsYes
evidenceNo
paginationYes
assumptionsNo
can_build_pathNo

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, and open-world, so the safety profile is covered. The description adds context annotations cannot: pagination semantics (1-indexed pages, 25 per page) and that router-scoped results carry extra evidence/can_build_path/assumptions fields that fabric-wide results lack. That last detail is a genuinely useful behavioral distinction between the two modes.

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 leading question-then-answer sentence front-loads purpose, and the input/output field blocks are easy to scan. Every sentence carries information, though the output field enumeration is partly redundant with the declared output schema.

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 list tool with annotations and an output schema, this covers scope selection, pagination, return payload shape, and endpoint equivalence—everything needed to call it correctly. Minor gaps remain around the meaning of the router-scoped evidence fields and any ordering or error behavior, but nothing blocking.

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 0%, so the description must carry all parameter meaning, and it does: it explains that graph_time is the IGP graph time, that router_id scopes to a router's resolved RIB view, and gives defaults for page and per_page. Only graph_time is thin—"the IGP graph time" is not much more than a restatement of the name—which keeps this below a 5.

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 gives a concrete verb+resource framing ("Answers 'which VNI/VRF exists on which leaf'") plus the two scopes: fabric-wide VPN/VRF/VNI inventory or a single router's view. It is far more specific than the name alone. It does not, however, distinguish itself from the sibling get_vrf_inventory, which an agent could reasonably confuse with this tool.

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

Usage Guidelines4/5

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

"router_id ... omit for the fabric-wide list" is explicit conditional guidance that tells the agent how to select between the two modes. It also names the equivalent REST endpoints, which anchors expected behavior. There is no statement of when to prefer this over get_vrf_inventory or other VPN/VRF-related siblings, so it stops short of full routing 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.