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

tplink-deco-mcp-server

by roquerodrigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Deco units

list_deco_nodes
Read-only

Retrieve all TP-Link Deco mesh units, including the gateway and satellites, with MAC, model, role, IP, firmware, internet status, and per-band backhaul signal details.

Instructions

List the Deco units that form the mesh: the gateway and every satellite.

Returns each unit's MAC, name, model, role (master is the gateway), LAN IP, hardware and firmware versions, internet status as the unit sees it, and the backhaul signal level per band.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 and the description doesn't need to repeat it. It does add genuine context beyond annotations: the set returned is the full mesh (gateway + every satellite) and the role field's `master` semantics are explained, which an agent cannot infer from the schema.

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?

Two sentences, front-loaded with the scope statement before the field enumeration. The return-field list is somewhat long and partially duplicates the output schema, but it is compact and reads as one clause rather than padding.

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 no parameters, an output schema, and read-only annotations, the description only needs to establish scope and the nature of the returned set, which it does. The field-by-field enumeration is redundant given the output schema exists; a mention of ordering or count would have been more valuable information to add.

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 the baseline is 4; there is nothing parameter-level the description could add. It correctly avoids wasting space on nonexistent arguments.

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 Deco units that form the mesh') and immediately scopes it as gateway plus satellites, which no sibling (list_clients, list_blocked_clients, list_address_reservations) covers. An agent can tell exactly what entity this returns.

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?

Usage is implied by the resource ('the units that form the mesh'), and the sibling set has no obvious overlapping alternative to route away from. However, there is no explicit when-to-use or when-not statement, and the relationship to get_internet_status (which also reports internet state) is left to inference.

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