Skip to main content
Glama
Sign In
AsusWRT MCP

AsusWRT MCP

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

asuswrt_restart_service

Restart an allowlisted service on AsusWRT or AsusWRT-Merlin routers over SSH, with optional dry-run and confirmation to safely recover a stopped or misbehaving service.

Instructions

Restart an allowlisted AsusWRT service.

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": {
      "service": "<service>"
    },
    "name": "asuswrt_restart_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
dry_runNo
serviceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only says 'restart' but does not disclose side effects, permission requirements, or what happens during the restart. The term 'allowlisted' is ambiguous without further context. Minimal transparency.

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 of 5 words, achieving brevity. However, it sacrifices substance. It could be more informative without becoming verbose, so it scores average on conciseness.

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?

For a tool that restarts a service (a potentially disruptive action), the description is extremely lacking. No output schema exists, no explanation of behavior on success/failure, and no elaboration on parameter usage. The description is not complete enough given the tool's complexity.

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?

Schema coverage is 0% and the description adds no meaning to the three parameters. It does not explain what valid 'service' values are, nor the roles of 'confirm' and 'dry_run'. The description fails entirely to compensate for the missing schema descriptions.

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?

Description clearly states the verb 'restart' and resource 'AsusWRT service'. It includes the qualifier 'allowlisted', which distinguishes it from generic service operations. However, it does not explicitly differentiate from siblings like 'asuswrt_service_processes' which might list services.

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 guidance on when to use this tool vs alternatives. No explanation of what 'allowlisted' means or under what conditions restarting is appropriate. The description lacks any when-to-use or when-not-to-use instructions.

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