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

tplink-deco-mcp-server

by roquerodrigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Forget client

remove_client
DestructiveIdempotent

Forget an offline device from the Deco client list so unused entries no longer appear; use blocking instead if you need to prevent reconnection.

Instructions

Forget a device that is no longer used, removing it from the client list.

Meant for offline devices: the router lists the device again as soon as it reconnects. This does not block it — use block_client for that.

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

Input Schema

NameRequiredDescriptionDefault
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.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the removal is transient and the device reappears on reconnect, which materially changes how an agent should use it. It stops short of noting any confirmation/permission requirements, so not 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 followed by the caveat and the alternative. No filler and nothing redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A destructive, idempotent single-parameter tool with full annotation coverage and an output schema; the description supplies the one thing structured data cannot — that the effect is temporary and differs from blocking. Nothing needed to call it correctly is missing.

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% and the single 'mac' parameter already documents both accepted formats. The description adds no meaning about the parameter beyond the schema, so the baseline 3 applies.

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 and resource ('Forget a device... removing it from the client list') and explicitly separates it from the blocking concept. An agent can distinguish it from block_client/unblock_client without opening 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 Guidelines5/5

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

Gives the operative condition ('Meant for offline devices'), explains the consequence that selects this tool over alternatives ('the router lists the device again as soon as it reconnects'), and names the alternative for the blocking case ('use block_client for that'). When-to-use, when-not-to-use and the alternative are all present.

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