Skip to main content
Glama

Topolograph

get_node_failure_reaction

Read-onlyIdempotent

Predict the whole-network impact if one or more routers go down.

Description: Whether the graph stays connected and which links see more or less traffic once these routers fail. A simulation only: nothing is changed in the graph.

Input fields: graph_time (str): The graph time failed_nodes (list[str]): Node names of the failed routers, e.g. ["10.10.10.2"]

Output fields: NetworkReactionResponse: the same keys as get_edge_failure_reaction.

Equivalent to POST /network-reaction/node-failure/.

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>",
      "failed_nodes": "<failed_nodes>"
    },
    "name": "get_node_failure_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
graph_timeYes
failed_nodesYes

Output Schema

NameRequiredDescriptionDefault
affectedLinksYes
disjointedNodesYes
isGraphStillConnectedYes

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?

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description adds real context on top: it is a simulation, no graph state is mutated, and the response shape mirrors get_edge_failure_reaction. It does not mention runtime cost of a whole-network simulation or any size limits on failed_nodes.

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 outcome, then constraints, then field docs - a sensible order. There is mild redundancy in restating a 'Description:' heading after an already descriptive lead sentence, but nothing is wasted beyond that.

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?

An output schema exists so return values need no explanation, and the description covers the simulation semantics, the sibling-equivalent response, and the REST endpoint. The only real gap is graph_time format/traceability, which matters for a two-parameter tool with no schema descriptions.

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 carries the burden. failed_nodes is well served with 'Node names of the failed routers' and a concrete example, but graph_time is only called 'The graph time' with no format or how it relates to get_all_graphs/get_graph_by_time, leaving one of two parameters under-specified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Predict the whole-network impact') with an explicit scope of node/router failure, and the closing 'Equivalent to POST /network-reaction/node-failure/' plus the reference to get_edge_failure_reaction makes clear it is the node-failure analogue rather than the edge-failure one. An agent can distinguish it from siblings without opening the schema.

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?

'A simulation only: nothing is changed in the graph' implies this is a safe what-if path, but there is no explicit when-to-use/when-not guidance and no direct pointer telling the agent to prefer get_edge_failure_reaction, it is only mentioned as having the same output keys. Usage is implied, not stated.

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.