Skip to main content
Glama

Topolograph

get_graph_analysis

Read-onlyIdempotent

Whole-graph report: central routers, most loaded links, single points of failure and more.

Input fields: graph_time (str): The graph time kind (str): central-nodes, most-loaded, single-point-of-failure, fault-tolerant, heatmap, unsym-paths, unidir-edges, backup-paths-in-ecmp, duplicated-terminated-networks or network-score at (str, optional): ISO 8601 moment; a watcher graph is shown with the events up to it

Output fields: dict with result, nodes and edges. The routers and links the report names are in nodes and edges; backup-paths-in-ecmp and duplicated-terminated-networks list rows in result.rows; network-score answers result.total, max, percentage and details.

Equivalent to GET /graph/{graph_time}/analyse/{kind}.

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": {
      "graph_time": "<graph_time>",
      "kind": "<kind>"
    },
    "name": "get_graph_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo
kindYes
graph_timeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish that the operation is read-only, idempotent, and nondestructive. Beyond that, the description discloses watcher-event cutoff behavior for at and kind-dependent differences in where results appear, although watcher semantics and any snapshot or computational constraints remain unclear.

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-first opening, labeled input and output sections, and compact endpoint mapping make the definition easy to scan. The long kind list is useful, but the output paragraph is dense and phrases such as "and more" and "The graph time" add little.

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?

The definition supplies enough information to construct many calls and usefully notes heterogeneous result locations, with an output schema also available. For a ten-mode analysis tool, it still leaves important gaps around the required graph_time value, selection among less-obvious report kinds, and how at interacts with non-watcher graphs.

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?

With 0% schema description coverage, the text adds substantial value by enumerating the accepted kind strings and documenting at as optional, ISO 8601-formatted, and tied to watcher events. However, graph_time is only tautologically described as "The graph time," with no accepted format or source, and less-obvious kinds such as fault-tolerant and unsym-paths are not explained.

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 opening identifies a whole-graph analysis report and concrete products such as central routers, heavily loaded links, and single points of failure, rather than merely restating the tool name. It substantively distinguishes analysis from raw graph retrieval, but does not explicitly contrast siblings such as get_graph_by_time or get_graph_status.

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?

The enumerated kind values provide concrete report choices, while the at description explains the context for supplying an optional event cutoff. There is no when-not guidance, prerequisite for obtaining graph_time, or direction to a raw-graph or status tool when analysis is unnecessary.

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.