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

tplink-deco-mcp-server

by roquerodrigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Internet status

get_internet_status
Read-only

Check whether the Deco mesh is online and diagnose internet outages by reporting WAN cable state, IPv4/IPv6 connection status, public WAN address, DNS servers, and gateway LAN address.

Instructions

Report whether the mesh is online and how the gateway reaches the provider.

Returns the WAN cable state, the IPv4 and IPv6 connection state (online/offline, protocol such as pppoe, router error code), the public WAN address with its gateway and DNS servers, and the gateway's LAN address. Use it to diagnose an internet outage.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
lanYes
wanYes
ipv4Yes
ipv6Yes
cable_statusYesPhysical WAN port state: `plugged` or `unplugged`.

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; the description adds useful behavioral context by specifying exactly which connectivity facts are inspected and that it reflects gateway/provider reachability rather than client-side state. It does not mention latency, caching, or whether the status is live-probed versus cached.

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?

The purpose and the diagnostic use case are front-loaded, followed by a compact field inventory. The parenthetical detail ('online'/'offline', protocol such as pppoe, router error code) is slightly dense but each item earns its place as concrete return content.

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 status tool with an output schema present, this description covers the essentials: what is checked, what categories of data come back, and when to reach for it. Nothing an agent needs in order to select and invoke it is missing.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Schema coverage is 100% regardless.

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: report whether the mesh is online and how the gateway reaches the provider, then enumerates the concrete fields involved (WAN cable state, IPv4/IPv6 state, public WAN address, LAN address). This makes it distinguishable in substance from siblings like get_router_performance, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

'Use it to diagnose an internet outage' gives a clear triggering scenario. There are no explicit exclusions or pointers to alternative tools (e.g. get_router_performance vs. this for uptime vs. WAN state), so it stops short of full when/when-not guidance.

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