Skip to main content
Glama

Topolograph

compare_bgp_routes

Read-onlyIdempotent

Diff BGP routes between two instants: one row per differing route.

Input fields: bgp_graph_time (str): The BGP graph epoch to query (the t1 epoch) t0 (str): ISO 8601 timestamp, the earlier instant t1 (str): ISO 8601 timestamp, the later instant router_id (str, optional): Scope the diff to one reporting speaker t0_graph_time (str, optional): Epoch of t0 when it differs from bgp_graph_time (collector restart); must be the same collector

Output fields: dict with key: items (list of BgpRouteDiffRow; diff_status is added|withdrawn|changed, a changed row also carries diff_prev). There is no total: count the rows per diff_status and quote those counts.

Equivalent to GET /bgp-graph/{bgp_graph_time}/routes/compare.

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": {
      "bgp_graph_time": "<bgp_graph_time>",
      "t0": "<t0>",
      "t1": "<t1>"
    },
    "name": "compare_bgp_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
t0Yes
t1Yes
router_idNo
t0_graph_timeNo
bgp_graph_timeYes

Output Schema

NameRequiredDescriptionDefault
itemsYes

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, so the description is free to add real operational context: diff_status values (added|withdrawn|changed), that changed rows carry diff_prev, that there is deliberately no total and callers should count per status. The collector-restart caveat on t0_graph_time ('must be the same collector') is a non-obvious constraint that annotations would never convey.

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?

Grouped into Input fields and Output fields, front-loaded with the one-sentence purpose, with every clause carrying information. The t0_graph_time entry wraps awkwardly across lines and repeats 'epoch', but there is no genuinely wasted sentence.

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?

Given 5 parameters at 0% schema coverage, an output schema, and annotation coverage of safety traits, the description fills the important gaps: parameter meanings, diff semantics, the absent total, and the compute-counts guidance. Minor omissions like pagination or expected row volume limits are the only shortfall.

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 must carry all parameter meaning, and it does: it distinguishes t0/t1 (earlier/later ISO timestamps) from bgp_graph_time and t0_graph_time (graph epochs), explains the t1 epoch mapping and the restart scenario for the optional field, and frames router_id as a speaker scope.

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?

States a specific verb ('Diff') plus resource ('BGP routes') and an explicit output shape ('one row per differing route'), which cleanly separates it from retrieval siblings like get_routes or search_bgp_routes without naming them. A one-line contrast with a plain route lookup would have made it a 5.

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?

The 'between two instants' framing implies when to reach for this over a plain route fetch, and the 'Equivalent to GET /bgp-graph/.../compare' line anchors it to a known operation. It never states when NOT to use it, nor does it name a sibling such as search_bgp_routes as the alternative for point-in-time queries.

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.