fios-mcp

by vehoelite

Overview Schema Source Related Servers Discussions Admin

Python

Local

reboot_router

Destructive

Reboots the Verizon Fios CR1000A router (about 4 minutes downtime); previews only unless confirmed.

Instructions

Reboot the router (~4 minutes of downtime). Without confirm, only previews.

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
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description goes beyond them by quantifying the impact (~4 minutes of downtime) and disclosing the safe-by-default preview behavior. It stops short of saying whether the router drops existing sessions or loses unsaved config, which would matter for a destructive operation.

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, no filler, with the operation and its cost front-loaded before the safety gate. Every clause contributes a fact the agent cannot get elsewhere.

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 one-parameter destructive tool with an output schema and explicit destructive annotations, the essentials are present: what it does, the cost, and the confirm gate. Minor omissions are what the preview returns and whether network connectivity is fully interrupted.

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

Parameters5/5

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

Schema description coverage is 0% and the confirm parameter has no description, so the description carries the full burden. It does exactly that: confirm absent/false means preview only, confirm true means execute, which is the single semantic detail an agent needs to avoid an accidental reboot.

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') with no ambiguity, and no sibling tool does anything similar, so confusion risk is low. The parenthetical downtime figure further narrows what the operation means in practice.

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

Usage Guidelines4/5

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

The phrase 'Without confirm, only previews' implicitly prescribes a two-step workflow: call without confirm first to preview, then with confirm to act. It does not name when a reboot is warranted versus alternatives like snapshot_config or apply_desired_state, but the destructive nature makes the intended usage clear.

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