Skip to main content
Glama

dhcp_reservation

Destructive

Manage DHCP address reservations on TP-Link routers: list leases, add or update MAC-to-IP mappings, remove reservations, and pin a client's current IP. Warns about randomized MACs.

Instructions

DHCP address reservations (stable IPs, e.g. for kiosk tablets). action=list (with lease status and random-MAC warnings) | leases | add (mac, ip, name) | update (mac + ip/name/enable) | remove (mac) | reserve_current (pin a client's CURRENT address; identify it by mac, current_ip or client hostname). MACs in any format. Warns when a MAC is randomised/private - that device must use its real MAC.

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_reservation"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNo
macNo
nameNo
applyNofalse (default) = dry run: show the plan, diff, warnings and risk, send nothing. true = send it.
actionNolist
clientNo
enableNo
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main
current_ipNo
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is known. The description adds real behavioral context beyond that: list returns lease status and random-MAC warnings, and randomised/private MACs trigger a warning because the device must use its real MAC. It says nothing about how changes are applied or that a dry run/confirm token exists, leaving the risk model partly implicit.

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?

The description is front-loaded with the resource definition and then densely enumerates actions in a pipe-delimited form, with no filler sentences. The terseness borders on cryptic (e.g. 'leases' has no explanation), but it is efficient and well ordered.

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 an 11-parameter destructive multi-action tool with no output schema, the description covers the action semantics and the notable warnings well, and the safety-critical parameters (apply, confirm_token, reveal, router) are documented in the schema itself. What is missing is any statement of return shape for the read actions and any indication of irreversibility for remove.

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

Parameters3/5

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

Schema description coverage is only 36% across 11 parameters, so the description has to compensate and it partly does — it explains mac, ip, name, enable, client (hostname), current_ip and the action values, plus notes MACs are accepted in any format. However, four parameters (apply, confirm_token, reveal, router) get no mention in the description; those are covered by schema descriptions, so the gap is reduced but not closed.

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?

The description names a specific resource (DHCP address reservations) with an illustrative use case (kiosk tablets) and enumerates the six supported actions, so the agent immediately knows what the tool manipulates. It does not explicitly distinguish itself from plausible siblings such as ip_mac_binding or dhcp_server_set, which keeps it below a 5.

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?

Each action carries an inline hint of its inputs and purpose (add needs mac/ip/name; update needs mac + one of ip/name/enable; reserve_current pins a client's CURRENT address identified by mac, current_ip or hostname). This effectively tells the agent which action to pick for which intent, but it offers no guidance on when to prefer this tool over the related dhcp_server_set or ip_mac_binding tools.

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