Skip to main content
Glama

Topolograph

get_route_events

Read-onlyIdempotent

Answers "did MAC/IP X move, from where, when": route event history (add/withdraw/MAC-move) of the BGP epochs bound to this graph.

Input fields: graph_time (str): The IGP graph time start_time (str, optional), end_time (str, optional): ISO 8601 window last_minutes (int, optional): Look back this many minutes; overrides start_time/end_time vni (int, optional), vrf (str, optional), rt (str, optional), rd (str, optional), prefix (str, optional), mac (str, optional): same route filters as get_routes page (int): Page number, 1-indexed (default: 1) per_page (int): Items per page (default: 50)

Output fields: dict: route and peer events interleaved by time; a route row carries moved_from_vtep when it is a MAC's arrival on a new VTEP.

Equivalent to GET /events/{graph_time}/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_route_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
rdNo
rtNo
macNo
vniNo
vrfNo
pageNo
prefixNo
end_timeNo
per_pageNo
graph_timeYes
start_timeNo
last_minutesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds real value beyond them by stating that last_minutes overrides start_time/end_time, that pagination is 1-indexed with a 50 default, and that route and peer events are interleaved by time. Those are the kind of non-obvious behaviors that belong here.

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?

Structure is strong: one-sentence purpose first, then a compact input list, then output, then the REST endpoint. The input list is dense but every line carries semantics. The output block mildly duplicates the existing output schema, though moved_from_vtep is genuine added information.

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, paginated, filtered event-history tool the description covers purpose, windowing/override behavior, filter reuse, pagination, and interleaved return shape, and an output schema exists so return values need no further expansion. Nothing an agent needs in order to call it correctly is missing.

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

Parameters3/5

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

With 12 parameters at 0% schema description coverage, the description carries the burden and mostly delivers: every parameter is listed with optionality flags, the override precedence for last_minutes is spelled out, and page/per_page defaults are stated. However, vni/vrf/rt/rd/prefix/mac are delegated wholesale to "same route filters as get_routes" with no format hints, and graph_time is glossed only as "the IGP graph time", so a few gaps remain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line frames the exact question answered ("did MAC/IP X move, from where, when") and names the resource: route event history with add/withdraw/MAC-move event types scoped to the BGP epochs bound to the graph. That contrast with get_routes (current state) versus this tool (history) lets an agent pick correctly without opening a schema.

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?

The question framing plus "route event history" gives clear context for when to reach for this over a route-lookup sibling, and the "same route filters as get_routes" line signals the parameter relationship. It stops short of explicit when-not guidance or naming get_routes/search_bgp_routes as the alternative for current state.

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.