Skip to main content
Glama

routing

Destructive

Manage static routes on TP-Link routers: list the live route table, then add, update, or remove entries with dry-run planning and confirmation.

Instructions

Static routes: action=list | system (the live routing table) | add (route={name, target, netmask, gateway, interface LAN|WAN, enable}) | update (name, route={...}) | remove (name).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "routing"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
applyNofalse (default) = dry run: show the plan, diff, warnings and risk, send nothing. true = send it.
routeNo
actionNolist
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main
confirm_tokenNoRequired with apply=true for CRITICAL changes: the token from the dry run (valid 5 minutes, bound to the exact plan and current router state).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false and non-idempotent, so the safety profile is covered. The description adds the per-action object shape but says nothing beyond annotations about irreversibility, the confirm_token requirement for critical changes, or that mutations default to a dry run — those live only in the 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?

A single front-loaded sentence with pipe-delimited actions — no wasted words and the resource appears first. The telegraphic style is dense but still parseable.

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 seven-parameter destructive CRUD tool with a dry-run/confirm-token safety protocol, the description covers action semantics but omits the mutation workflow that an agent most needs to sequence correctly. The router, reveal and apply semantics are left entirely to the schema, and there is no output schema to compensate.

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 coverage is 57% and the 'route' parameter is a bare object with no sub-properties, so the description's expansion to route={name, target, netmask, gateway, interface LAN|WAN, enable} is genuinely additive. It also clarifies which parameters pair with update/remove (name) versus add (route).

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?

Names the resource (static routes) and enumerates all five operations with what each acts on, including the useful distinction that action=system shows the live routing table while action=list shows configured static routes. It is only slightly weakened by not contrasting itself with the sibling tool literally named 'system'.

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 action enumeration implies when each mode applies, but there is no explicit guidance on choosing between list vs system, no mention of the dry-run-then-apply-then-confirm_token workflow, and no statement of prerequisites or when not to use this tool.

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