Skip to main content
Glama

Topolograph

get_all_graphs

Read-onlyIdempotent

Description: This tool retrieves available graphs from the Topolograph API with optional filtering. This tool is a first step for all analysis. Each graph reports two monitoring flags: - is_monitored: the graph was received from a watcher (vs manually uploaded). Only monitored graphs have events; use is_monitored=true when answering change/event questions. - is_live: the source watcher is currently sending heartbeats.

Input fields: protocol (str, optional): Filter graphs by protocol (ospf, ospfv3, isis, yaml) area (str, optional): Filter graphs by area number is_monitored (bool, optional): true = only watcher-received graphs, false = only manually uploaded name (str, optional): Case-insensitive substring over graph_time or watcher_name (e.g. "before_maintenance") latest_only (bool, optional): Return only the single newest graph among those matching the filters page (int): Page number, 1-indexed (default: 1) per_page (int): Items per page (default: 50)

Output fields: dict with keys: items: list of graphs, each with is_monitored and is_live flags pagination: page, per_page, total, total_pages

Equivalent to GET /graph with query parameters.

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

Input Schema

NameRequiredDescriptionDefault
areaNo
nameNo
pageNo
per_pageNo
protocolNo
latest_onlyNo
is_monitoredNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint). The description adds real semantic context beyond them: the meaning of the is_monitored and is_live flags, that only monitored graphs have events, and that the call maps to GET /graph. It stops short of noting rate limits, auth requirements, or result-size caveats.

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 purpose statement followed by labeled Input/Output sections and a flag glossary; the nesting makes it scannable rather than a wall of text. Minor waste exists in restating output keys that an output schema already declares, and in the 'Description:' label on the first line.

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?

For a seven-parameter, zero-required listing tool, the definition covers filtering semantics, flag interpretation, and pagination, which is what an agent needs to call it correctly; the output schema handles return shape. The one noticeable gap is that it never says what identifier to carry forward from a returned graph into the downstream analysis tools.

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

Parameters5/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 completely: it documents all seven parameters, including the protocol value set (ospf, ospfv3, isis, yaml), the surprising semantics of name (case-insensitive substring over graph_time or watcher_name), the true/false split for is_monitored, latest_only's 'single newest among those matching the filters', and pagination defaults.

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 and resource ('retrieves available graphs from the Topolograph API') plus the scope-limit ('with optional filtering'), and adds that it is the first step for all analysis. It does not explicitly name a sibling it differs from, so it falls short of the 5 bar, but an agent can still tell this is the broad graph-listing entry point rather than an analysis tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

'This tool is a first step for all analysis' and 'use is_monitored=true when answering change/event questions' give real when-to-use guidance tied to a concrete task. It does not name alternatives (e.g., get_graph_by_time or get_graph_analysis) or state when to avoid this tool, so no explicit routing is provided.

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.