Skip to main content
Glama

Topolograph

list_bgp_graphs

Read-onlyIdempotent

List BGP graph epochs (one per BMP collection cycle), newest first.

Input fields: page (int): Page number, 1-indexed (default: 1) per_page (int): Items per page (default: 50)

Equivalent to GET /bgp-graphs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bgp_graphs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
per_pageNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 needs no restating. The description adds genuine behavioral context beyond that: result ordering (newest first), what an epoch represents, and pagination defaults. It does not discuss result size or limits, 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 core purpose and ordering are front-loaded in the first sentence, then parameters are laid out in a scannable list extending the pagination pattern used by siblings. The "Equivalent to GET /bgp-graphs" line is marginal but not wasteful for API-aware agents.

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

Completeness4/5

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

This is a simple two-optional-parameter list tool with an output schema, so return values need not be described, and the description covers scope, ordering, and pagination. Nothing essential to invoking it correctly is missing; only explicit alternative routing would add value.

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 must carry parameter meaning, and it does document both fields with types and defaults. However, most of that merely restates the schema's own type/default declarations; the only real added meaning is "1-indexed" for page. Adequate but thin compensation for the coverage gap.

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 ("List BGP graph epochs") and adds a clarifying gloss, "one per BMP collection cycle," plus an ordering guarantee ("newest first"). It does not explicitly contrast itself with siblings like get_bgp_graph or get_all_graphs, 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 only implied: the epoch/collection-cycle gloss hints this is the enumeration endpoint to call before fetching a specific graph, but there is no explicit when-to-use, when-not-to-use, or named alternative. The "Equivalent to GET /bgp-graphs" line helps agents that map to the REST API but is not selection guidance.

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.