Skip to main content
Glama

router_raw_read

Read-onlyIdempotent

Sends read-only operations to catalogued router forms, including custom read requests, and refuses write-type actions to safely inspect TP-Link Archer settings.

Instructions

Send a read-only operation to any catalogued form, e.g. path='iptv?form=setting', operation='read', or custom read ops like operation='getBlockHistory' with fields. Refuses write-type operations.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
fieldsNoextra request fields (strings; objects are JSON-encoded)
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main
operationNoread

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the description is consistent with them. It adds real behavioral value by disclosing that write-type operations are actively refused at call time, and it shows the free-form operation idiom rather than only a fixed enum. Return shape and error detail beyond 'refuses' are unstated.

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?

Two compact sentences front-load the capability and pack the examples efficiently; nothing is padded. The phrase 'with fields' is slightly ambiguous and could be clearer, but overall the text earns its length.

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 raw passthrough tool with five parameters, nested fields object and no output schema, the description covers the calling idiom but not how to discover valid paths/operations (the catalog sibling is only referenced indirectly via router_status in the schema). An agent still needs external knowledge of available forms to use it confidently.

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 60%, and the description compensates for the undocumented 'operation' parameter by giving example values, including a non-default custom read op ('getBlockHistory'), and shows the expected path syntax with a query-form example. 'fields' usage is mentioned but only loosely ('with fields'), and reveal/router semantics are left entirely to the schema.

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 and resource: send a read-only operation to any catalogued form, and it distinguishes itself from the write sibling by explicitly refusing write-type operations. What it lacks is a direct pointer to router_get/router_catalog for structured reads, so the differentiation from the non-raw readers is only implied.

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?

Concrete usage examples are given (path='iptv?form=setting', operation='read', operation='getBlockHistory' with fields) plus the exclusion that write ops are refused. However, there is no explicit 'prefer router_get/router_catalog when a structured tool exists' guidance, leaving the agent to infer when the raw escape hatch is appropriate.

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