Skip to main content
Glama

reboot_router

Destructive

Restarts the router to recover from connectivity issues, temporarily dropping the whole network and internet for a minute or two. Requires confirm=true to proceed.

Instructions

Reboot the router. The whole network and the internet drop for a minute or two. Needs confirm=true.

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

NameRequiredDescriptionDefault
confirmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds genuinely new context: the blast radius (entire network plus internet), the approximate outage duration, and the confirm=true gate. It does not cover auth requirements or whether the reboot is reversible/interruptible, so it stops short of full disclosure.

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?

Three short sentences, zero filler, with the action and its consequence front-loaded and the required input last. Every sentence contributes a distinct fact (what, impact, precondition).

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

Completeness4/5

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

For a single-parameter destructive tool with annotations and an output schema present, the description supplies the operational essentials: impact scope, duration, and the confirmation requirement. Only marginal details (permissions, behavior on confirm=false) are absent, which is acceptable given the surrounding structured data.

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 description coverage is 0% and the single 'confirm' parameter defaults to false, so the description must carry the meaning. It does so by stating the parameter must be set to true, giving the agent the exact value needed rather than just the type, though it doesn't explain what happens if it is omitted or false.

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?

States a specific verb ('Reboot') and resource ('the router') in the first sentence, which is unambiguous against siblings like router_change, router_run, or router_status. The follow-up sentence clarifies the scope of the action (whole network and internet), further separating it from narrower router operations.

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 conveys the cost of use ('the whole network and the internet drop for a minute or two') and a hard precondition ('Needs confirm=true'), which implicitly tells the agent to use this only when an outage is acceptable. However, it never explicitly says when to prefer this over siblings such as router_change or router_run, so guidance is implied rather than stated.

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