tplink-deco-mcp-server

Overview Schema Source Related Servers Discussions Admin

Router performance

get_router_performance

Read-only

Retrieve current gateway CPU/memory usage, online client count, and summed real-time download/upload rates to assess mesh network load.

Instructions

Report how busy the gateway is and how much traffic flows through the mesh right now.

Returns CPU and memory usage of the gateway in percent, the number of online clients and the summed instantaneous download and upload rates of every client, in kilobytes per second.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`online_clients`	Yes
`cpu_usage_percent`	Yes
`memory_usage_percent`	Yes
`total_upload_kilobytes_per_second`	Yes	Sum of every client's upload rate.
`total_download_kilobytes_per_second`	Yes	Sum of every client's download rate.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, non-open-world operation, and the description adds useful behavioral context: instantaneous traffic, aggregate client rates, and units in percent and kilobytes per second. It does not discuss permissions, rate limits, or failure behavior, but those are less critical for this zero-param read-only tool.

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 two efficiently structured sentences. The first gives purpose and the second enumerates return metrics, with no wasted text.

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?

For a zero-parameter, read-only performance snapshot tool with an output schema and read-only annotations, the description is complete enough to call correctly. It explains the current-time scope and the metrics being reported.

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?

There are zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and none are present to misunderstand.

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?

The description states a specific verb/resource pair: report gateway/mesh performance. It also lists the exact metrics returned, so the tool is easy to identify. However, it does not explicitly differentiate itself from siblings such as get_internet_status.

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?

The only usage signal is "right now," which implies a current snapshot rather than historical data. There is no explicit guidance on when to use this tool instead of siblings like get_internet_status or list_clients.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server