Skip to main content
Glama

dhcp_leases

Read-onlyIdempotent

Retrieve active DHCP leases from a TP-Link router or modem to view connected devices' hostnames, IP addresses, MAC addresses, and remaining lease times.

Instructions

Active DHCP leases: hostname, IP, MAC, lease time left.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so safety and repeatability are covered. The description adds that only *active* leases are returned (implying no historical or expired entries), which is genuinely useful scope information beyond the annotations, but says nothing about result volume or ordering.

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?

A single compact clause with zero filler, front-loaded with the resource name and then the payload fields. It is a fragment without a verb, which makes it read as a label rather than an instruction, but no sentence is wasted.

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?

A zero-parameter read tool with an output schema and full annotation coverage needs very little prose, and this supplies the key scope fact (active only) plus the returned fields. Only the absence of any routing hint toward dhcp_reservations / client_history / ipv6_status keeps it from being complete.

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 takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. It correctly spends no words on input semantics and instead describes the payload.

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?

Names the specific resource ('Active DHCP leases') and enumerates the fields each lease carries (hostname, IP, MAC, lease time left), so an agent knows exactly what it will get. The qualifier 'Active' quietly separates it from the static 'dhcp_reservations' sibling, though no sibling is named outright.

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 when-to-use guidance, no statement of prerequisites, and no mention of an alternative tool for related questions such as reservations or client history. The agent must infer from the field list alone that this is the right call for 'what's connected right now' questions.

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