omada-mcp

by falehsub

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Diagnose gateway WAN & VPN health

diagnose_wan

Read-onlyIdempotent

Correlate live WAN link state, latency/packet loss, speedtest, VPN tunnel health, and gateway alerts/events…

Instructions

Correlate live WAN link state, latency/packet loss, speedtest, VPN tunnel health, and gateway alerts/events…

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

Input Schema

Name	Required	Description	Default
`site`	No
`hours`	No
`includeSpeedtest`	No

Output Schema

Name	Required	Description	Default
`wan`	Yes
`findings`	Yes
`warnings`	Yes
`nextSteps`	Yes
`recentLogs`	Yes
`vpnSummary`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.0Nov 15, 2026
- addedInput schema / properties / site
```
Added value: +{
+  "type": "string"
+}
```
First observedv1.2.2Nov 13, 2026

TDQS

C2.8/5.0

Behavior3/5

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

The annotations already declare this as read-only, idempotent, open-world, and non-destructive. The description adds that the tool correlates multiple live telemetry sources including speedtest and alerts/events, but it does not disclose the impact of triggering a speedtest or how the time window affects correlation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and compact, but it ends with an ellipsis, indicating it is incomplete rather than deliberately concise. The listed data sources are useful but are not structured as actionable guidance.

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?

For a composite diagnostic tool with three undocumented parameters and a default speedtest action, the description is incomplete. Because an output schema exists, return values need not be described, but the definition still lacks scope, selection guidance against siblings, and parameter semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It only hints at the speedtest parameter by naming 'speedtest' among the correlated sources; it does not explain 'site' scoping or what the 'hours' window controls.

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 uses a specific verb, 'Correlate,' and lists concrete resources: WAN link state, latency/packet loss, speedtest, VPN tunnel health, and gateway alerts/events. This makes the composite diagnostic purpose clear, though it does not explicitly distinguish itself from siblings like get_wan_status or list_vpn_tunnels.

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?

There is no explicit guidance on when to use this tool instead of get_wan_status, list_vpn_tunnels, or diagnose_client. The title implies diagnostic use, but the description leaves the agent to infer when this correlated view is preferable to simpler status tools.

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