Skip to main content
Glama

Topolograph

list_bgp_bindings

Read-onlyIdempotent

List the BGP-to-IGP graph bindings known for a BGP graph epoch.

Output fields: dict with key: items (list of BgpBinding)

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

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": "list_bgp_bindings"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgp_graph_timeYes

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds the return shape (items of BgpBinding) and the equivalent REST endpoint, but says nothing about pagination, empty results, or what an epoch-scoped lookup implies when the epoch is stale.

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?

Front-loaded with the action, then output shape, then the REST equivalence in three tight lines with no filler. The output-fields block is somewhat redundant given an output schema exists, but it remains short.

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?

Annotations cover safety and an output schema covers return values, so the remaining burden is small. Still, for a tool keyed on a single opaque epoch parameter, the missing format guidance and the absence of any tie-in to sibling lookup tools leave a real gap.

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 coverage is 0% for the single required parameter, so the description carries the burden. It only restates the concept as 'a BGP graph epoch' and echoes the path template {bgp_graph_time}; it never states the accepted format (ISO timestamp, integer epoch, opaque id), which is exactly what an agent needs to supply a valid value.

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 (List) and resource (BGP-to-IGP graph bindings) scoped to a BGP graph epoch, which is enough to distinguish it from the singular get_bgp_binding. It does not explicitly name the sibling it contrasts with, so it stops short of 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never says when to call this versus get_bgp_binding, list_bgp_graphs, or the other graph tools, and gives no prerequisites or exclusions. The only implicit cue is that you need a bgp_graph_time, which the reader must infer from the sentence itself.

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.