tplink-mcp

Overview Schema Source Related Servers Discussions Admin

set_wireless_syspara

Configure advanced wireless radio parameters for a band—WMM, AP isolation, beacon/DTIM, RTS/frag thresholds, and group-key updates. Restarts the radio and requires confirmation.

Instructions

Set the advanced radio parameters for a band — WMM, AP isolation, beacon interval, DTIM period, RTS/fragmentation threshold, group-key update interval. ⚠️ Restarts the radio; clients on the band drop briefly. Requires confirm=True.

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": {
      "band": "<band>"
    },
    "name": "set_wireless_syspara"
  }
}

Input Schema

Name	Required	Description	Default
`wmm`	No
`band`	Yes
`dtim`	No
`confirm`	No
`ap_isolation`	No
`rts_threshold`	No
`frag_threshold`	No
`beacon_interval`	No
`group_key_update`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 26, 2026

TDQS

A3.7/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the critical behavioral traits: the radio restarts, clients on the band drop briefly, and confirm=True is required. Some secondary details such as permissions or reversibility are absent, but the key destructive impact is clearly stated.

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?

The description is compact and front-loaded: it states the action, lists the configurable parameters, then immediately gives the restart warning and confirm requirement. Every sentence adds useful information with no padding.

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

Completeness3/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 explained. But for a 9-parameter disruptive mutation tool with no annotations and 0% schema descriptions, the description omits units, band-value format, and null/default behavior, so it is only partially complete for correct invocation.

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 0% across 9 parameters, so the description must compensate. It names all the major fields and the confirm requirement, but it does not explain units, allowed band values, ranges, defaults, or what null/omitted values do, leaving important parameter semantics unspecified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: set advanced radio parameters for a band, and enumerates WMM, AP isolation, beacon interval, DTIM, RTS/fragmentation threshold, and group-key update. It is clear what the tool does, but it does not explicitly distinguish itself from close siblings like set_wireless_advanced or set_wifi_band.

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?

The description gives a precondition (confirm=True) and a warning that the radio restarts, which implies this is a disruptive advanced configuration tool. However, it does not explicitly say when to use this instead of set_wireless_advanced, get_wireless_advanced, or set_wifi_band, so alternative selection 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.