Skip to main content
Glama

Get Router Page

get_router_page
Read-onlyIdempotent

Reads allowlisted router data pages (ARP, connections, logs, UPnP, firmware), truncating long lists and redacting secrets.

Instructions

Read one allowlisted router data page: arp (ARP table), net_connections, log, upnp or firmware (version info). Long lists are truncated to limit. Fields that look like secrets (passwords, keys, tokens) are returned as "[redacted]". Response shapes are firmware-specific; see docs/endpoints.md.

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

Input Schema

NameRequiredDescriptionDefault
pageYes
limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world safety, yet the description adds real behavioral detail: long lists are silently truncated to `limit`, secret-looking fields come back as '[redacted]', and response shapes vary by firmware. It stops short of covering failure modes (e.g., a page unsupported by the current firmware) or whether truncation is signaled in the output.

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?

Front-loaded with the verb and resource, then the page enum, then behavioral caveats — a good information ordering with no filler sentences. The density is high, though the 'see docs/endpoints.md' pointer relies on out-of-band documentation rather than standing alone.

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?

With an output schema present, the description need not describe return values, and it correctly defers shape details to docs while disclosing truncation and redaction. For a two-parameter read tool this is close to complete; only error/unsupported-page behavior is left unspecified.

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 the parameter meaning, and it largely does: it explains that `page` selects one of five specific data sets and gives concrete glosses ('arp (ARP table)', 'firmware (version info)') beyond the bare enum strings, while noting `limit` caps truncated output. It still omits the default, maximum, and truncation-indication semantics of `limit`.

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 concrete verb ('Read') plus the resource ('one allowlisted router data page') and enumerates the five valid pages with brief glosses for arp and firmware. The allowlist enumeration itself scopes the tool against siblings, but it never states a relation to adjacent tools such as router_status or list_devices, which could plausibly return overlapping device data.

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?

Usage is implied by the enumerated page set rather than stated: an agent can infer it should call this for raw arp/net_connections/log/upnp/firmware dumps. There is no explicit when-to-use versus when-not guidance and no mention of alternatives for overlapping data like device lists.

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