fios-mcp

Overview Schema Source Related Servers Discussions Admin

add_dhcp_reservation

Idempotent

Reserve a DHCP IP for a device MAC on a Fios router. The two-phase process rejects .100-.150 to avoid conflicts with Verizon-reserved addresses.

Instructions

Reserve an IP for a MAC. Refuses .100-.150 (reserved for Verizon devices). Two-phase.

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": {
      "mac": "<mac>",
      "ip": "<ip>"
    },
    "name": "add_dhcp_reservation"
  }
}

Input Schema

Name	Required	Description	Default
`ip`	Yes
`mac`	Yes
`name`	No
`confirm`	No
`replace`	No
`expected_etag`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the bar is lower. The description adds genuine value by disclosing the .100-.150 refusal rule, but 'Two-phase' is cryptic: it does not say what the first phase returns or that the second requires confirm=true, which is exactly the behavior an agent would get wrong.

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?

Three front-loaded fragments with no filler, but the terseness crosses into under-specification: 'Two-phase.' conveys almost nothing on its own, so brevity here costs comprehension rather than aiding it.

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

Completeness2/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 6-parameter mutation tool with 0% schema coverage the description leaves the confirm/replace/expected_etag interaction entirely opaque. The two-phase protocol and the replace-versus-conflict path are the core things an agent needs and are missing.

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

Parameters2/5

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

Schema description coverage is 0% across 6 parameters, so the description must carry the load and it does not. name, replace, expected_etag (an optimistic-concurrency token) and confirm are all completely unexplained, and 'Two-phase' only vaguely points at confirm.

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 ('Reserve an IP for a MAC'), which is unambiguous and clearly distinct from sibling tools like list_dhcp_reservations and delete_dhcp_reservation. It stops short of naming those siblings explicitly, so it is clear but not fully differentiated.

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?

There is no guidance on when to use this versus delete_dhcp_reservation or list_dhcp_reservations, nor on when to set replace or confirm. The fragment 'Two-phase' gestures at a workflow but does not tell the agent the sequence or prerequisites.

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