omada-mcp

by falehsub

Overview Schema Source Related Servers Discussions Admin

Python

Remote

List VPN tunnels & secret-redacted configs

list_vpn_tunnels

Read-onlyIdempotent

List WireGuard, OpenVPN, IPsec, and SSL/L2TP VPN tunnel state and configured profiles…

Instructions

List WireGuard, OpenVPN, IPsec, and SSL/L2TP VPN tunnel state and configured profiles…

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

Input Schema

Name	Required	Description	Default
`site`	No

Output Schema

Name	Required	Description	Default
`counts`	Yes
`tunnels`	Yes
`warnings`	Yes
`configuredVpns`	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

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds the scope of data returned (live state plus configured profiles) but says nothing about redaction of secrets beyond what the title hints, nor about result volume or site scoping.

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?

A single front-loaded sentence with no filler, but it trails off with an ellipsis, leaving the sentence unfinished and giving the impression that meaningful content was cut.

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?

The tool is simple and an output schema exists, so return values need not be explained. However, the meaning of the only input parameter and any guidance on when to prefer a diagnostics tool are missing, which leaves the definition thin relative to its practical use.

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?

There is exactly one parameter (site) with 0% schema description coverage, and the description never mentions it. An agent cannot learn from the description whether site narrows results to one site or is required for multi-site accounts, so the single gap is unaddressed.

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 ("List") and a specific resource (VPN tunnels), and enumerates the covered technologies (WireGuard, OpenVPN, IPsec, SSL/L2TP) plus the two data classes (tunnel state, configured profiles). An agent can distinguish it from generic siblings like list_devices or list_wans, 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 Guidelines2/5

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

The description offers no when-to-use guidance, no exclusions, and no pointer to an alternative (e.g., a status/diagnostics tool such as diagnose_wan) when the agent wants tunnel troubleshooting rather than a list. Usage is only implied by the verb "List".

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