Skip to main content
Glama
Sign In
tplink-mcp

tplink-mcp

by axo4xo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_reservations

Retrieves DHCP address reservations from a TP-Link router, returning each reservation's MAC address, IP, hostname, comment, and enabled status.

Instructions

DHCP address reservations: [{mac, ip, comment, hostname, enable}].

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden and delivers almost none of it. It does not state that this is a read-only operation, whether results are paginated or filtered, or what permissions are required.

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?

One short fragment with no filler, which is good for brevity, but it is not a complete sentence and leads with a label rather than a front-loaded statement of what the tool does. It is terse to the point of under-specification.

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 the description needn't explain return values — yet the only content it offers is a partial return-shape sketch. With no annotations and a purpose that is only implied, the definition leaves the agent without the purpose or usage context needed to choose it over dhcp_leases.

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, so parameter_semantics gets the baseline 4; there is nothing for the description to clarify. The field list in the description actually refers to return values, not inputs, so it adds no parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase listing the fields of DHCP reservations rather than a verb+resource statement. It restates the tool name (list_reservations) with a hint of the item shape, so a reader can infer listing behavior but the tool never says 'list' or 'retrieve' explicitly, and it doesn't distinguish itself from dhcp_leases or list_clients.

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?

No when-to-use guidance, no mention of alternatives, and no distinction from the closely related dhcp_leases or add_reservation/remove_reservation siblings. The agent must infer that this returns static reservations rather than dynamic leases entirely from the name.

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

Deploy Server

Other Tools