Skip to main content
Glama
Sign In
AsusWRT MCP

AsusWRT MCP

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

asuswrt_vpn_server

Toggle the OpenVPN server on compatible Asus routers over SSH. Set enabled to true or false, with optional dry-run and confirmation.

Instructions

Enable or disable the OpenVPN server toggle.

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": {
      "enabled": "<enabled>"
    },
    "name": "asuswrt_vpn_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
dry_runNo
enabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are present, so the description must bear the full burden of transparency. It only states that the tool enables/disables the toggle, but fails to disclose side effects, required permissions, or what happens to the server state. Basic mutation behavior is implied, but no depth is provided.

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

Conciseness3/5

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

The description is a single sentence, making it very concise. However, it lacks any structure such as parameter explanations or usage notes. While it is front-loaded, it sacrifices completeness for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given three parameters and no output schema or annotations, the description is severely incomplete. It does not explain the optional parameters (confirm, dry_run), nor does it describe expected outcomes or error conditions. This is insufficient for an agent to use the tool correctly.

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

Parameters1/5

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

The schema has 0% description coverage, and the description adds no meaning to the parameters. It does not explain what 'confirm' or 'dry_run' do, nor the implications of 'enabled' beyond the boolean toggle. The description adds no value over the bare parameter names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: to enable or disable the OpenVPN server toggle. It specifies the exact action (enable/disable) and the resource (OpenVPN server toggle), distinguishing it from sibling tools like asuswrt_vpn_overview which provides status.

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?

No guidelines are provided on when to use this tool versus alternatives. The description does not mention any prerequisites, conditions, or when not to use it. Siblings like asuswrt_vpn_overview exist, but no differentiation is offered.

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