Skip to main content
Glama
Sign In
tplink-mcp

tplink-mcp

by axo4xo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remove_reservation

Deletes a DHCP reservation by MAC address so the TP-Link router stops assigning that device its reserved IP.

Instructions

Delete the DHCP reservation for a MAC.

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>"
    },
    "name": "remove_reservation"
  }
}

Input Schema

NameRequiredDescriptionDefault
macYes

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?

With no annotations, the description carries the full burden for a destructive operation, but says nothing about irreversibility, required permissions, or what happens if no reservation matches the MAC. Only the bare mutation verb is conveyed.

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?

One front-loaded sentence with no filler; the target resource and identifier come first. Brevity is appropriate, though it leaves room to add essential detail without bloat.

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?

For a one-parameter delete with no annotations and no output schema, the description should at least state the MAC format and the failure/not-found behavior. As written, an agent has enough to guess the call but not enough to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single 'mac' parameter, so the description must compensate and does not: no MAC address format (colon/dash/case), no statement that it must match an existing reservation exactly. It only restates that a MAC identifies the target.

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?

Specific verb plus resource ('Delete the DHCP reservation') with the selecting key (MAC) stated. It is clearly distinct from siblings add_reservation and list_reservations by name, though it never names them explicitly.

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 or when-not-to-use guidance, and no mention of alternatives such as add_reservation or set_dhcp_settings. The agent must infer that removal requires an existing 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