Skip to main content
Glama
Sign In
AsusWRT MCP

AsusWRT MCP

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

asuswrt_vlan_guest_status

Inspect VLAN and guest segmentation state using redacted counts to check network isolation and guest access configuration.

Instructions

Inspect VLAN and guest segmentation state using redacted counts only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important trait: output is limited to redacted counts rather than full configuration. It omits auth requirements, whether any state is mutated, and what the counts represent.

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?

A single front-loaded sentence with no filler. The wording is slightly terse ('redacted counts') but nothing is wasted.

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 no-param, no-annotation, no-output-schema read tool, the description is minimal but workable. Since there is no output schema, more detail about what the counts cover (VLAN IDs? guest SSIDs? client counts?) would help the agent interpret results.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The 'redacted counts only' note is relevant to output rather than parameters.

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 clear verb (Inspect) and specific resource (VLAN and guest segmentation state), which is distinguishable from the guest-focused siblings like asuswrt_guest_networks and asuswrt_guest_lan_access. It does not, however, explicitly contrast itself with those overlapping guest-segmentation siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'redacted counts only' implies this is the privacy-preserving alternative for segmentation checks, but no when-to-use condition or named alternative is given. The agent must infer when this tool is preferred over the guest_* siblings.

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

Deploy Server

Other Tools