Skip to main content
Glama

dhcp_reservations

Read-onlyIdempotent

Retrieves the router's fixed IP address reservations so you can review which devices are assigned static DHCP addresses.

Instructions

Fixed IP reservations (address reservation) configured on the router.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, closed-world behavior. The description adds that the information concerns configuration on the router, but provides no further context about completeness, freshness, or behavior when no reservations exist.

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?

The single compact phrase is front-loaded with the resource and its router configuration scope. The parenthetical terminology is useful clarification rather than unnecessary repetition.

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 zero-argument, read-only tool with an output schema, this is nearly sufficient to select and invoke correctly. An explicit retrieval verb and a brief distinction from active DHCP leases would remove the remaining ambiguity.

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?

The tool has no parameters, so there are no argument semantics requiring explanation. The zero-argument schema is sufficient for invocation, and the description adequately identifies the requested resource.

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 clearly identifies the resource as fixed-IP/address reservations configured on the router, adding useful meaning beyond the tool name. However, it does not explicitly say that the tool lists or retrieves those reservations, nor does it explicitly distinguish them from siblings such as dhcp_leases.

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 explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The word "configured" provides some scope, but the agent must infer any distinction between inspecting reservations, viewing leases, and using client or static-IP tools.

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