Skip to main content
Glama

Topolograph

list_bgp_nodes

Read-onlyIdempotent

List the BGP speakers of a BGP graph epoch.

Input fields: bgp_graph_time (str): The BGP graph epoch to query role (str, optional): Filter by node role asn (str, optional): Filter by autonomous system number page (int): Page number, 1-indexed (default: 1) per_page (int): Items per page (default: 50)

Output fields: dict with keys: items (list of BgpNode, each with rib_view, can_build_path, observed_by), pagination

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

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

Input Schema

NameRequiredDescriptionDefault
asnNo
pageNo
roleNo
per_pageNo
bgp_graph_timeYes

Output Schema

NameRequiredDescriptionDefault
itemsYes
paginationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real context beyond that: pagination defaults (page 1, per_page 50), the output envelope (items + pagination), and the underlying REST endpoint equivalence. It says nothing about rate limits, error behavior, or ordering of results, so it is useful but not rich.

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 sentence is front-loaded and the field lists are cleanly separated into input and output sections. The per-parameter type annotations slightly duplicate the schema, but with 0% schema coverage that redundancy is functional rather than wasteful. No filler prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter filtered list tool with an output schema already present, the description covers everything an agent needs: what it returns at a high level, defaults, filters, and the required epoch argument. Nothing essential to correct invocation is missing.

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

Parameters4/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 and does so: all five parameters are listed with type, optionality, default, and a plain-language meaning (e.g. 'Filter by autonomous system number'). It falls short of a 5 because 'role' has no enumerable values given and the expected format of bgp_graph_time is never specified.

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 opens with a specific verb+resource+scope: 'List the BGP speakers of a BGP graph epoch.' That is far more precise than the name alone and tells an agent it is reading nodes scoped to a single graph epoch. It does not explicitly contrast with siblings like get_bgp_node_route_summary or list_bgp_sessions, 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 Guidelines3/5

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

Usage is implied by 'of a BGP graph epoch', which signals the tool requires a graph time and is not a general node listing. There is no explicit when-to-use/when-not-to-use guidance and no named alternative for route-level or binding-level queries among the many sibling tools. An agent can infer the fit but must do the work 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.