Skip to main content
Glama
Sign In
tplink-deco-mcp-server

tplink-deco-mcp-server

by roquerodrigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List fixed IPs

list_address_reservations
Read-only

Lists DHCP address reservations so you can see which fixed IPs are assigned to specific MAC addresses, their device names, and the router’s reservation limit.

Instructions

List the fixed IPs the DHCP server always hands to the same device.

Returns each reservation's MAC and IP with the device name the mesh shows for that MAC (null when the device is not on the client list), and the most reservations the router accepts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
reservationsYes
maximum_reservationsYesMost reservations the router accepts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already carry the safety profile (readOnlyHint=true, openWorldHint=false), so the description's job is to add context. It does disclose the return shape (MAC, IP, device name, null when offline) and a capacity note about the max number of reservations, but with an output schema present most of this is duplicated structured data. No pagination, ordering, or scope caveats are given.

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?

Three short clauses, front-loaded with the purpose, then the return contents, then the capacity note. Every sentence carries information and nothing is repeated.

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 parameterless read tool with full annotation coverage and an output schema, the description supplies everything needed to select and call it. Minor gaps only: no mention of ordering or whether reservations outside the DHCP range appear, but these are unlikely to affect invocation.

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 there is nothing for the description to disambiguate; the baseline for a 0-param tool is 4. No misleading parameter claims are made.

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

Purpose5/5

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

States a specific verb ('List') and resource ('fixed IPs the DHCP server always hands to the same device'), which unambiguously identifies static DHCP reservations. This distinguishes it from sibling tools like list_clients and the add/update/remove_address_reservation mutations without requiring the schema.

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 read-only listing nature is implied by 'List' and reinforced by the readOnlyHint annotation, but there is no explicit when-to-use guidance or contrast with alternatives such as list_clients or the reservation mutation tools. An agent must infer that this is the inspection counterpart to add_address_reservation.

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