Skip to main content
Glama

Topolograph

get_bgp_binding

Read-onlyIdempotent

Fetch one BGP-to-IGP graph binding: which IGP graph this BGP epoch is correlated with, and how confidently (matched_rids, source_coverage, state).

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

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

Input Schema

NameRequiredDescriptionDefault
graph_timeYes
bgp_graph_timeYes

Output Schema

NameRequiredDescriptionDefault
stateYes
matched_ridsYes
bgp_graph_timeYes
igp_graph_timeYes
source_coverageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real semantic context about what the binding represents (correlation plus confidence via matched_rids, source_coverage, state) and pins it to a REST endpoint, but says nothing about behavior when no binding exists or how partial coverage should be read.

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 tight sentences: the core purpose and returned concepts come first, the API equivalence second. Every clause carries information and nothing is redundant.

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 the description needn't enumerate return values, and the safety profile is fully covered by annotations. The remaining gaps are the undocumented time parameter formats and the absence of any guidance on how to use this versus the many neighboring binding/graph tools.

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 two required parameters, so the description must carry the burden. It only reveals the parameters' roles and order through the URL template (bgp_graph_time then graph_time); it never states the expected format (epoch vs ISO timestamp) or what the distinction between the two time values means.

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 uses a specific verb ("Fetch") on a precisely named resource ("one BGP-to-IGP graph binding") and spells out the semantic content: which IGP graph a BGP epoch correlates with plus confidence fields. The singular "one" implicitly separates it from list_bgp_bindings and get_bgp_graph, but it never names a sibling explicitly.

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 guidance: no condition that selects this over list_bgp_bindings, get_bgp_graph, or get_network_by_graph_time, and no exclusions or prerequisites. The agent must infer from the required time parameters that this is a point lookup for a specific BGP/IGP pair.

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.