Skip to main content
Glama

network_unroute

Stops an active network route so intercepted requests resume reaching the network normally. Use it to remove routing rules set up earlier.

Instructions

Stop a route network_route set up, so its requests reach the network again.

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": {
      "route_id": "<route_id>"
    },
    "name": "network_unroute"
  }
}

Input Schema

NameRequiredDescriptionDefault
route_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the post-condition ('requests reach the network again') but not what happens to requests already captured or paused by the route, whether the operation is idempotent, or what occurs with an unknown route_id — all material for a teardown tool with zero annotation coverage.

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?

A single tight sentence with the effect front-loaded and no filler. Minor awkwardness in 'a route network_route set up' slightly hampers scanning but does not waste words.

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?

For a simple one-parameter teardown tool with no output schema, the core purpose and end-state are covered. However, with no annotations and an undocumented parameter, the definition should still clarify error behavior and the fate of in-flight intercepted requests.

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?

There is a single parameter, route_id, and the schema has 0% description coverage, so the description must compensate. Saying 'its requests' implies route_id identifies the intercepted route established earlier, which adds some meaning, but it never states the identifier's expected format or origin beyond that implicit link.

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 states a specific verb ('Stop') and resource ('a route network_route set up'), and it explicitly names the sibling tool that created the route, so the agent can distinguish it from network_route itself. The phrasing 'Stop a route' is slightly awkward — the real action is removing a request interception — but 'so its requests reach the network again' makes the effect concrete.

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 implied rather than stated: use this after network_route has installed an interception, to undo it. The description names its counterpart tool, which is a useful routing cue, but it never explicitly says when to call this versus simply navigating away, nor what preconditions exist (e.g., a valid route_id from network_route).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.