Skip to main content
Glama

router_run

Destructive

Executes a selected router operation, such as DHCP renewal or PPP disconnection, and previews the action unless confirm=true.

Instructions

Run a router operation from router_objects' list, such as ACT_DHCP_RENEW or ACT_PPP_DISCONN. Without confirm=true it only shows what it would do.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo
operationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds critical behavior beyond that: the confirm=true gate and dry-run default. It does not describe irreversible effects, required permissions, or the exact preview output, so it falls short of full transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two compact sentences with no wasted wording. The main action is front-loaded, and the important confirm/preview behavior is stated immediately after.

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 destructive router operation with no output schema and no schema parameter descriptions, the definition covers the essential call mechanics: operation source, examples, and the confirm gate. It could be stronger by explicitly stating irreversibility and permission requirements, but annotations already flag destructiveness.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It does this well for both parameters by identifying that operation values come from router_objects' list and by explaining that confirm=true controls execution versus preview, though it lacks exact allowed value formatting.

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 gives a specific verb and resource: run a router operation from router_objects' list, with concrete examples such as ACT_DHCP_RENEW and ACT_PPP_DISCONN. It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools like router_change or reboot_router.

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?

It explains that without confirm=true the tool only previews what it would do, which implies a preview-then-execute workflow. However, it does not state when to use this tool versus alternatives such as router_change, nor does it provide explicit exclusions.

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