Skip to main content
Glama

Topolograph

get_bgp_graph

Read-onlyIdempotent

Fetch one BGP graph epoch by bgp_graph_time.

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

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

Input Schema

NameRequiredDescriptionDefault
bgp_graph_timeYes

Output Schema

NameRequiredDescriptionDefault
nodesNo
sessionsNo
timestampYes
graph_timeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description adds only a REST endpoint equivalence ('GET /bgp-graph/{bgp_graph_time}'), which conveys little beyond that — nothing about error behavior for unknown timestamps, response size, or latency.

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 short sentences, the primary action first, with no filler. Nothing could be removed without losing information, though much more could usefully have been added.

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?

An output schema exists, so return-value documentation is not required, and annotations cover the safety profile. However, for a tool whose sole parameter is undocumented in the schema, leaving its format unexplained renders the definition only barely sufficient to invoke correctly.

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 the single required parameter, so the description must carry the burden and it does not: 'bgp_graph_time' is only restated, with no format (ISO-8601 string? opaque epoch id? relative offset?) or example value. The one unresolved ambiguity is exactly the input an agent must produce to call the tool.

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 description gives a specific verb and resource — 'Fetch one BGP graph epoch' — and names the key that selects it, which distinguishes it from list-style siblings like list_bgp_graphs. It does not explicitly contrast itself against the many other get_* graph tools, but the singular 'one epoch' scope is clear.

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 bgp_graph_time' suggests the caller must already possess a specific epoch timestamp, whereas listing or analysis tools would be used otherwise. There is no explicit when-to-use statement, no stated alternative such as get_graph_by_time or get_graph_analysis, and no exclusions.

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.