Skip to main content
Glama

dhcp_server_set

Destructive

View or change DHCP server settings, including enable/disable, pool start/end, lease time, gateway, and DNS, with validation and dry-run planning before applying.

Instructions

DHCP server: action=get shows settings; otherwise change enable / start / end (pool) / lease_minutes (1-2880) / gateway / dns1 / dns2. Validated against the LAN subnet, the router's own IP, active leases and reservations. Disabling DHCP or a gateway other than the router is CRITICAL.

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

Input Schema

NameRequiredDescriptionDefault
endNo
dns1No
dns2No
applyNofalse (default) = dry run: show the plan, diff, warnings and risk, send nothing. true = send it.
startNo
actionNoset
enableNo
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main
gatewayNo
confirm_tokenNoRequired with apply=true for CRITICAL changes: the token from the dry run (valid 5 minutes, bound to the exact plan and current router state).
lease_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructive=true and non-idempotent, but the description adds real behavioral context: changes are validated against the LAN subnet, the router's own IP, active leases and reservations, and two classes of change are marked CRITICAL. It does not restate the confirm-token/dry-run mechanics, which live in the schema, so the addition is complementary rather than duplicative.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences with the read/write split front-loaded and the risk warning last, where it carries weight. The telegraphic 'start / end (pool)' phrasing is efficient rather than sloppy, though the sentence is long enough that a skimming agent could miss the validation clause.

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 12-parameter destructive mutation with no output schema, the description covers the field semantics, the validation surface, and the risk classification an agent needs before calling. The only material omission is the apply/confirm_token safety flow, which is documented in the schema rather than lost.

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 only 33%, and the description compensates well by naming the mutable fields (enable, start, end as the pool, gateway, dns1, dns2) and adding a constraint the schema lacks entirely: lease_minutes is bounded to 1-2880. The remaining undocumented parameters (apply, reveal, router, confirm_token) all carry their own schema descriptions, so little is lost.

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 resource (DHCP server) and splits behavior clearly into action=get for reading and the mutable field list for setting. An agent can tell what the tool does without opening the schema, though it never names or contrasts a sibling such as dhcp_reservation or lan.

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 get-vs-set branch is explicit and is effectively a when-to-use rule, and the CRITICAL note steers away from disabling DHCP. However, there is no guidance on when to prefer this over dhcp_reservation or lan, and the dry-run/apply path is left to the schema rather than called out as the recommended workflow.

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