Skip to main content
Glama
Sign In
tplink-mcp

tplink-mcp

by axo4xo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_wps

Enable or disable WPS globally on a TP-Link router to control Wi-Fi Protected Setup access.

Instructions

Enable or disable WPS globally.

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": {
      "enabled": "<enabled>"
    },
    "name": "set_wps"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the setting is global, but not whether changes persist, require reboot, affect connected clients, or have security consequences, which are important for a WPS mutation.

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 front-loaded sentence with no filler; every word contributes to the action and scope.

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?

An output schema exists, so return values need not be described, and the single boolean is simple. However, with no annotations and no behavioral details, the definition is thin for a mutation that changes a global wireless security setting.

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 0% and the single boolean has no description in the schema. The phrase 'Enable or disable' implies true/false semantics for enabled and adds global scope, but it does not explicitly state the mapping or any constraints.

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 pair (enable/disable) and resource (WPS) with global scope, which clearly separates it from the sibling get_wps read operation. An agent can identify the mutation target 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 Guidelines2/5

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

No when-to-use guidance, prerequisites, or alternatives are given. It does not say when to prefer this over get_wps for inspection or when toggling WPS may be inappropriate, such as security implications.

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