Skip to main content
Glama

router_raw_write

Destructive

Sends arbitrary operations and fields to catalogued router forms when no specific tool fits, using dry-run plans, risk warnings, and confirm tokens for CRITICAL changes.

Instructions

Escape hatch: send ANY operation + fields to a catalogued form. Risk comes from the catalog (unknown ops are CRITICAL, so need a confirm_token). FORBIDDEN ops (factory reset, config restore, firmware upload, quick setup, cloud bind) also need TPLINK_ALLOW_FORBIDDEN=1. Prefer the specific tools.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
applyNofalse (default) = dry run: show the plan, diff, warnings and risk, send nothing. true = send it.
fieldsNorequest fields (strings; objects are JSON-encoded)
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main
operationYes
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

A4.5/5.0
Behavior5/5

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

Beyond the destructive and non-readOnly annotations, it discloses the risk model (unknown ops are CRITICAL), the confirm_token requirement for CRITICAL changes, the forbidden-operation list and the TPLINK_ALLOW_FORBIDDEN=1 gate, plus that apply defaults to a dry run. That is exactly the operational context an agent needs before invoking a destructive tool.

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?

Three dense sentences, front-loaded with the escape-hatch framing and finishing with the routing advice. Nearly every clause carries weight, though the parenthetical forbidden-op list is long enough to feel like a lookup table in prose.

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, no-output-schema tool, the description covers risk tiers, confirmation, forbidden operations and alternatives. It doesn't say how an agent discovers valid operations (router_catalog is unnamed) or what reveal does, leaving a small gap for a raw escape hatch.

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 71% and the schema already documents apply, reveal, router and confirm_token. The description still adds meaning for confirm_token by tying it to CRITICAL risk from the catalog, and clarifies that fields are operation-specific strings, which the schema does not explain.

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 ('send ANY operation + fields to a catalogued form') and frames it as an escape hatch, which distinguishes it clearly from router_raw_read and the domain-specific tools.

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?

It says 'Prefer the specific tools', giving an explicit when-not-to-use, and 'escape hatch' implies the fallback case. It does not spell out the positive trigger for using raw write over a specific tool, but the routing intent is unmistakable.

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