Skip to main content
Glama

Topolograph

get_edge_failure_reaction

Read-onlyIdempotent

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

Description: Same shape as get_node_failure_reaction, for links instead of nodes: whether the graph stays connected, and the traffic rerouting pattern (which links see more/less traffic). This is a simulation only: it does not fail any link or otherwise mutate the graph.

Input fields: graph_time (str): The graph time failed_edges (list[list[str]]): Pairs of node names identifying each failed link, e.g. [["10.10.10.1", "10.10.10.2"]]

Output fields: NetworkReactionResponse: dict with keys: - isGraphStillConnected: bool - affectedLinks: {sptPathsIncreasedInPercent, sptPathsDecreasedInPercent}, each a list of {edge_key, from, to, value}, one per link direction, value in percent - disjointedNodes: list of node-name groups, if the graph split

Equivalent to POST /network-reaction/edge-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_edges": "<failed_edges>"
    },
    "name": "get_edge_failure_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
graph_timeYes
failed_edgesYes

Output Schema

NameRequiredDescriptionDefault
affectedLinksYes
disjointedNodesYes
isGraphStillConnectedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by emphasizing that this is a simulation only and that it does not fail any link or mutate the graph, although the output field details largely duplicate the output schema.

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 description is front-loaded with purpose and organized into clear sections. Some content, particularly the output fields list, is redundant given the output schema, but the structure remains clear and readable.

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 simulation tool with annotations and an output schema, the description covers the essentials: purpose, inputs, outputs, and non-mutating behavior. The main gap is the lack of format or semantics for graph_time.

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 the burden. It gives a strong example and meaning for failed_edges, but graph_time is described only as 'The graph time', which is too vague to compensate fully for the missing schema documentation.

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?

The description states a specific verb and resource: predict whole-network impact if links go down. It distinguishes itself from get_node_failure_reaction by explicitly saying it is the link equivalent, so an agent can identify it 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 Guidelines4/5

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

The description clearly places the tool in context by contrasting it with get_node_failure_reaction for nodes versus links. It does not explicitly state when not to use it, but the distinction is sufficiently clear for routing.

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.