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

tplink-deco-mcp-server

by roquerodrigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Wi-Fi configuration

get_wifi_configuration
Read-only

Retrieve every Wi-Fi network's SSID, enabled state, broadcast bands, and hidden flag, plus each radio's channel, width, and 802.11 mode; optionally include passwords.

Instructions

Describe the Wi-Fi networks the mesh broadcasts and how each radio is tuned.

Returns every network (main, guest, iot, mlo) with its SSID, whether it is enabled, the bands it is broadcast on and whether it is hidden, plus each radio band's channel, channel width, 802.11 mode and backhaul channel. Passwords are left out unless include_passwords is set.

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": "get_wifi_configuration"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_passwordsNoAlso return each network's password. Only set it when the user explicitly asks for a password, such as to share the guest network. Default: false.

Output Schema

NameRequiredDescriptionDefault
radiosYes
networksYes

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 cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower, and the description still adds real behavioral value: it discloses the full return surface (SSID, enabled state, bands, hidden flag, channel, width, 802.11 mode, backhaul channel) and, importantly, the privacy default that passwords are withheld unless explicitly requested. It does not discuss staleness/caching of the configuration snapshot, which is the only notable gap.

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?

One summary sentence front-loads the purpose, followed by a compact enumeration of the returned fields and the password default. No filler, no restatement of the title, and the most decision-relevant caveat (passwords excluded) lands last where it is read before calling.

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?

An output schema exists, so return values need not be described, yet the description still sketches them well enough to set expectations. For a zero-required-parameter, read-only configuration tool with annotations covering safety, nothing an agent needs in order 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 parameter already documents its default and the 'only when the user explicitly asks' guidance, so the baseline of 3 applies. The description reinforces the consequence — 'Passwords are left out unless `include_passwords` is set' — but adds no syntax or format detail beyond what the schema states.

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?

The description opens with a specific verb+resource pair — describing the Wi-Fi networks the mesh broadcasts and how each radio is tuned — and then enumerates the concrete entities returned (main/guest/iot/mlo networks, per-radio band settings). That scope is unmistakably different from every sibling (clients, nodes, internet status, reservations), so an agent can select it 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 Guidelines3/5

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

Usage is only implied: the description makes clear this is the read path for Wi-Fi configuration, and the note that passwords are omitted unless `include_passwords` is set hints at the read-only inspection workflow. But there is no explicit when-to-use/when-not, no naming of an alternative tool, and no prerequisite context (e.g. that it requires an authenticated session to the mesh).

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