Skip to main content
Glama

Topolograph

get_vrf_inventory

Read-onlyIdempotent

Router-scoped VRF inventory as of an IGP graph: names, route distinguishers, and per-address-family import/export route targets.

Input fields: graph_time (str): The IGP graph time router_id (str, optional), rd (str, optional): Filters

Output fields: dict with key: items (list of Vrf)

Equivalent to GET /graph/{graph_time}/vrfs.

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_vrf_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
rdNo
router_idNo
graph_timeYes

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds a genuinely useful trait beyond that — the result is a point-in-time snapshot 'as of' a graph time — but says nothing about what happens with a missing/unknown graph_time or how large the inventory response can be.

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?

Front-loaded one-sentence purpose followed by compact input/output field lists and endpoint equivalence; nothing is redundant. The line-wrapped formatting of the opening sentence is slightly awkward but costs nothing semantically.

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?

The output schema exists, so restating 'dict with key: items' is optional but harmless. The main gaps for a 3-parameter temporal query tool are the absence of sibling differentiation (e.g. vs list_vpns) and any note on behavior when graph_time is not a valid graph — the description does not close those.

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 is the only source of parameter meaning, and it does label all three fields (graph_time as the IGP graph time, router_id and rd as filters) while the phrase 'router-scoped' hints that router_id scopes the result and 'route distinguishers' hints at rd. It stops short of giving formats or explaining what rd matches against.

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 first sentence names a specific resource (VRF inventory), a scope (router-scoped, snapshot at an IGP graph time), and the returned content (names, RDs, per-AF import/export route targets). It does not, however, distinguish this from probable siblings such as list_vpns, so the agent must infer the distinction from the resource name alone.

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 statement of when to use this tool versus alternatives, no prerequisites (e.g. whether a graph must exist first, obtainable via get_all_graphs), and no exclusions. The only usage-adjacent information is the REST endpoint equivalence, which is not decision 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.