tplink-mcp

Overview Schema Source Related Servers Discussions Admin

reboot_router

Restart a TP-Link router through the MCP server to recover connectivity or apply changes. Requires confirm=true before execution to prevent accidental reboots.

Instructions

Reboot the router. Must be called with confirm=True to actually reboot.

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

Input Schema

Name	Required	Description	Default
`confirm`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 26, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden, and it does disclose the critical safety gate: the call is a no-op unless confirm=True. It omits the operational consequences an agent needs — expected downtime, dropped sessions/connections, and irreversibility of the action.

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, zero waste, with the action stated first and the gating condition immediately after. Nothing could be removed without losing meaning.

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?

An output schema exists, so return values need not be explained. But for a destructive reboot operation with no annotations, the description should mention service interruption and that the device will be unreachable during restart; that gap leaves an agent under-informed about side effects.

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?

Schema coverage is 0%, so the description must compensate, and it does: it explains that confirm is a boolean switch whose True value is required to trigger the reboot, with the default otherwise being a no-op. That is the essential semantic an agent needs beyond the raw boolean type.

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 specific verb and resource ('Reboot the router'), which is unambiguous and distinct from every sibling tool (none of which reboot). It stops short of differentiating itself from any specific alternative, but the action is inherently unique in this set.

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?

The description gives one operational condition — confirm=True is required to actually execute — which is a real usage constraint. However, it offers no guidance on when a reboot is appropriate (e.g., after a firmware update or as a troubleshooting step), nor any warning about when not to use it.

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