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

tplink-deco-mcp-server

by roquerodrigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Reserve fixed IP

add_address_reservation
Idempotent

Reserve a fixed IP address for a device that lacks one; the device obtains it on next DHCP renewal or reconnect. Use update instead when a reservation already exists.

Instructions

Reserve a fixed IP for a device that has none yet.

The device picks the address up on its next DHCP renewal or reconnect. Use update_address_reservation when the device already has one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mac": "<mac>",
      "ip": "<ip>"
    },
    "name": "add_address_reservation"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesIPv4 address inside the LAN, such as `192.168.68.50`.
macYesMAC address of the device, `AA:BB:CC:DD:EE:FF` or `AA-BB-CC-DD-EE-FF`.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false and closed-world, so the safety profile is covered. The description adds genuinely new behavior the annotations cannot express: the reservation only takes effect on the device's next DHCP renewal or reconnect, which matters for an agent verifying success. It does not mention what happens on conflicting existing reservation, which would push this to a 5.

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 sentences, front-loaded with the action and its precondition, followed by effect timing, then the sibling routing. No sentence is redundant.

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?

With an output schema present and full parameter documentation, the description only needs to cover intent, timing and routing, which it does. The one residual gap is conflict behavior (what occurs if a reservation for that MAC or IP already exists) for a tool that is a non-idempotent-in-practice 'add'.

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 100%, with both mac and ip fully documented including formats and an example, so the baseline is 3. The description adds no additional parameter meaning, but none is needed.

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 (Reserve) and resource (a fixed IP) plus a scoping precondition that is decisive: the device has none yet. That precondition alone distinguishes it from update_address_reservation without the agent needing to inspect either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative sibling, update_address_reservation, and the exact condition that selects it ('when the device already has one'). The agent has a complete routing decision between the two write paths.

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