Skip to main content
Glama

remove_router

Removes a saved router from the MCP configuration without contacting or changing the device. Use it by name to clean up stale router entries.

Instructions

Forget a router (does not touch the device).

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important trait: the device is left untouched, so this is a local registry operation rather than a remote mutation. It does not say whether forgetting is reversible, whether it purges cached credentials or connection history, or what happens when the name is unknown.

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 the caveat immediately after, with zero wasted wording. The extreme brevity borders on under-specification, but nothing is redundant or buried.

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 tool takes one simple parameter. What remains missing is the meaning of the "name" key and the failure behavior for a nonexistent router, which is a modest gap rather than a blocking one.

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?

Single required string parameter named "name" with 0% schema description coverage, so the description should clarify the identifier. It omits whether "name" is the same key used in add_router, a hostname, or an arbitrary label, leaving the only real parameter unexplained.

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 ("Forget a router") and the parenthetical distinguishes it from a device-level removal, which separates it from siblings like ros_remove. It stops short of naming that sibling explicitly, so the differentiation relies on the reader's inference.

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?

The parenthetical "does not touch the device" is an implicit exclusion signal: it tells the agent this is bookkeeping only and not the tool for unprovisioning hardware. However, there is no explicit when-to-use statement, no named alternative for actual device removal, and no precondition such as whether the router must already be registered.

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