Skip to main content
Glama

router_objects

Read-onlyIdempotent

Lists router web UI settings object names and their available operations, with optional name filtering, so you can identify the correct settings group before inspecting or changing it.

Instructions

Names of every settings object the router's web UI uses (LAN_WLAN, LAN_DHCP_STATIC_ADDR, WAN_IP_CONN_PORTMAPPING, FIREWALL, ...) and the operations it can run (ACT_REBOOT, ...). Filter with contains.

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_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is fully covered. The description adds that the names originate from the router's web UI, which explains their terse, device-specific form, but it does not say whether the list is static or fetched live, or whether unknown device models yield different vocabularies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, no filler, with the parenthetical example lists doing heavy lifting to convey the exact identifier style. The filtering hint is placed last where it belongs, after identity is established.

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?

There is no output schema, so the description must convey the return shape, and it only roughly does: examples plus an ellipsis suggest a flat collection of identifier strings but never say whether settings objects and operations are grouped, ordered, or formatted. For a discovery tool whose entire value is the returned vocabulary, that is a meaningful remaining gap.

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?

With one parameter and 0% schema description coverage, the description carries the burden — and it does explain that 'contains' is a filtering mechanism. However, it does not specify substring vs. prefix matching, case sensitivity, or whether multi-term input is supported, so the semantics remain partly guesswork.

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 names the resource precisely — the router's settings-object identifiers and operation identifiers — and gives concrete examples (LAN_WLAN, LAN_DHCP_STATIC_ADDR, ACT_REBOOT), so an agent knows it is a vocabulary/discovery call. It lacks an explicit verb ('list'/'return') and never names the siblings (router_read, router_run, router_change) that consume these names, so differentiation is left to inference.

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 only implied: by describing itself as a catalog of object and operation names, it hints that it precedes router_read/router_run, but it never states when to call it or when to skip it. The one explicit instruction, 'Filter with contains,' is parameter usage rather than tool selection guidance.

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