Skip to main content
Glama

router_catalog

Read-onlyIdempotent

Lists all TP-Link router forms with operation risk levels and live/copied verification status; filter by text or inspect one form's fields, key, and secrets.

Instructions

List every router form (219+), what each operation does to risk (read/normal/critical/forbidden) and whether its format is verified live or only copied from the web UI. filter narrows by text; path describes one form (fields, key, secrets).

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": "router_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
filterNo
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main

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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds a trust signal beyond that: each form's format is either verified live or only copied from the web UI, which should make an agent more cautious about unverified entries. It mentions that path returns fields, key, and secrets, but does not mention any cost, caching, or staleness caveats for the 219+ entry listing.

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 sentences carry a lot of meaning and lead with the main capability, and the parameter notes follow in a compact clause. The parentheses around 219+, risk levels, and (fields, key, secrets) make the text dense to read, but no sentence is wasted.

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?

Given that there are four optional parameters, no output schema, and annotations that already cover safety, this definition covers what is needed: it describes what is cataloged, how to filter, and how to drill into a single form. It is slightly short on interaction rules between path and filter and on the shape of returned entries, but the risk-level and verification vocabulary gives the agent enough context to use the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: reveal and router are documented in the schema, while path and filter have no schema descriptions. The description partly compensates by explaining that filter narrows by text and path selects and describes one form, but it does not say whether path and filter can be combined, or what happens when path fails to match any form. The baseline of 3 applies when schema coverage is partial, and here the description only slightly exceeds that baseline.

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 uses a specific verb-plus-resource phrase ("List every router form (219+)") and explains exactly what the listing contains: per-operation risk level and whether the format was verified live or copied from the web UI. It also spells out the second mode (path = one form). It never names the closest siblings such as router_get or router_raw_read, so it leaves the agent to infer the difference between this catalog read and a direct form read.

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 implies how to use the tool: use filter to narrow the list, use path to describe a single form. It does not say when to prefer this catalog over siblings like router_get or router_raw_read, nor when path should be used instead of filter. That leaves the key routing decision to inference.

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