Skip to main content
Glama

Topolograph

get_bgp_route_state

Read-onlyIdempotent

Point-in-time BGP route state, reconstructed from stored events.

Input fields: bgp_graph_time (str): The BGP graph epoch to query at (str, optional): ISO 8601 timestamp; defaults to now

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

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

Input Schema

NameRequiredDescriptionDefault
atNo
bgp_graph_timeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond them: the state is reconstructed from stored events rather than read live, meaning results are a derived snapshot with the consistency implications that carries, and 'at' defaults to now. It does not say what happens for an unknown or future epoch, which keeps it from a 5.

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 purpose is front-loaded in the first sentence and the remaining lines are a compact parameter list plus a REST endpoint mapping, all of which earn their place given zero schema coverage. The 'Input fields' block is somewhat redundant-looking in formatting but justified here; nothing needs trimming.

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?

With only two parameters, one required, an output schema present, and annotations covering the safety profile, the definition is largely sufficient to invoke the tool. The remaining gaps are how an agent should obtain a valid bgp_graph_time and how this snapshot tool relates to the other route-reading siblings, both of which matter for correct selection.

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?

Schema description coverage is 0%, so the description carries the full burden. It does define both parameters ('the BGP graph epoch to query', 'ISO 8601 timestamp; defaults to now'), which is real added value and explains the optional default. However, the expected string form of bgp_graph_time (ID vs. timestamp, and where the agent obtains one) is left ambiguous, and the operational meaning of querying across epochs is not explained.

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 opening sentence names a specific resource (BGP route state) and a specific mode (point-in-time, reconstructed from stored events), which is more informative than a bare 'get routes'. It stops short of 5 because it never distinguishes itself from siblings such as get_routes, search_bgp_routes, or get_bgp_node_route_summary, so the agent must guess which of several route-reading tools applies.

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 when-to-use or when-not-to-use statement, and no alternative is named despite a crowded family of route tools. The only implicit cue is 'point-in-time', which hints at a historical snapshot without saying so explicitly or telling the agent how it differs from a filtered search or a comparison call.

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.