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

tplink-deco-mcp-server

by roquerodrigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List clients

list_clients
Read-only

List devices known to a TP-Link Deco mesh and return each MAC address, name, IP, online status, network, and connection details so you can find a device's MAC for other client tools.

Instructions

List the devices (phones, computers, TVs, IoT gadgets) the mesh knows about.

Returns each device's MAC, name, IP, whether it is online, the network it joined (main, guest, iot, mlo), how it connects (wired or the radio band), its category, the Deco unit it is attached to, its instantaneous download/upload rate and whether QoS prioritizes it. The MAC is the key every other client tool takes; find it here first when the user names a device.

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

Input Schema

NameRequiredDescriptionDefault
online_onlyNoLeave out devices that are not connected right now. Default: false.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds real context by spelling out that this is a discovery step whose MAC feeds every other client tool. Much of the return-field listing is redundant with the output schema, but the 'find it here first' convention is genuine added value.

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?

The purpose is front-loaded in the first sentence and the practical routing tip comes last where it is easy to retain. The middle enumeration of return fields is long and partially duplicates the output schema, which keeps it from being maximally tight.

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 one-optional-parameter read tool with annotations and an output schema, this is close to sufficient: purpose, when-to-use and the MAC-as-key convention are all covered. The only gap is that the online_only filter is left entirely to the schema.

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 coverage is 100% and the single optional parameter online_only is fully documented in the schema, so the baseline of 3 applies. The description never mentions filtering at all, so it adds nothing over the structured field.

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 ('List the devices... the mesh knows about') and enumerates the device classes covered (phones, computers, TVs, IoT gadgets), which distinguishes it from the Deco-node and blocked-client list tools. The closing note that the MAC returned here is the key every other client tool takes makes its role in the family unmistakable.

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

Usage Guidelines4/5

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

Explicitly tells the agent when to reach for it: 'find it here first when the user names a device.' It gives clear positive guidance but no exclusion, such as when to prefer list_blocked_clients instead, so a 4 rather than a 5.

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