Skip to main content
Glama

Topolograph

get_bgp_node_route_summary

Read-onlyIdempotent

Route totals for one BGP speaker: its resolved RIB view size, a per-RIB-tag histogram, and how many routes it advertised (Adj-RIB-Out).

Equivalent to GET /bgp-graph/{bgp_graph_time}/node/{router_id}/routes/summary.

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

Input Schema

NameRequiredDescriptionDefault
router_idYes
bgp_graph_timeYes

Output Schema

NameRequiredDescriptionDefault
totalYes
by_ribsYes
rib_viewYes
adj_rib_outYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior, so the description is not burdened with safety disclosure. It does add substantive content beyond annotations by enumerating what is aggregated (RIB view size, per-tag histogram, Adj-RIB-Out count), which tells the agent this is a cheap aggregate call rather than a route listing; it stops short of noting whether counting is over a full RIB or a filtered view.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both earning their place: the first front-loads the returned data, the second pins the equivalent REST endpoint. No filler, no restatement of the tool name.

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 two-parameter read tool with full annotations and an output schema, the description supplies the core semantic content (what is summarized) without needing to describe the return shape. The remaining gap is the undocumented parameter formats, which matters given 0% schema coverage.

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

Parameters2/5

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

Schema description coverage is 0% for both required parameters, so the description carries the burden, and it only partially discharges it via the endpoint template GET /bgp-graph/{bgp_graph_time}/node/{router_id}/routes/summary. That mapping hints that router_id identifies the speaker and bgp_graph_time selects the snapshot, but neither the format (timestamp vs. graph ID) nor validity constraints are stated.

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 resource and scope: route totals for ONE BGP speaker, broken out as resolved RIB view size, a per-RIB-tag histogram, and Adj-RIB-Out advertised count. The 'one speaker' scoping implicitly distinguishes it from list/search siblings like search_bgp_routes or get_routes, though no sibling is named explicitly.

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 only implied by the scope phrase 'one BGP speaker' and the REST endpoint reference. There is no explicit when-to-use guidance, no statement of when to prefer this over get_routes, get_bgp_route_state, or search_bgp_routes, and no prerequisites such as whether the speaker must exist in the given graph time.

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.