omada-mcp

by falehsub

Overview Schema Source Related Servers Discussions Admin

Python

Remote

List gateway policy routing rules

list_policy_routes

Read-onlyIdempotent

List policy routing rules (gracefully reports unavailability if no gateway exists).

Instructions

List policy routing rules (gracefully reports unavailability if no gateway exists).

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

Input Schema

Name	Required	Description	Default
`site`	No

Output Schema

Name	Required	Description	Default
`count`	Yes
`items`	Yes
`warnings`	Yes
`supported`	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.2/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 the safety profile is fully covered. The parenthetical adds one genuinely new behavioral fact — that the call degrades gracefully when no gateway exists — which helps an agent interpret a non-result, but nothing else about the call is disclosed.

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?

One front-loaded sentence plus a short parenthetical; nothing is padded. It is arguably over-terse given the undocumented parameter, but no sentence is wasted.

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, and the tool is simple with one optional parameter. Still, the 'site' parameter's meaning and the scope of the policy routing rules being listed are left unaddressed, which leaves a small but real gap.

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% for the single optional 'site' parameter, and the description says nothing about it — not its format, whether it filters or scopes, or what happens when it is omitted. The description therefore fails to compensate for the schema gap.

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 names a specific verb and resource: 'List policy routing rules'. That is clearly distinct from siblings such as list_static_routes or list_acls, though it never explicitly contrasts itself with those routing-related siblings, so the differentiation is implicit rather than stated.

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?

Usage is only implied — an agent can infer this is the read path for gateway policy routing rules. There is no explicit statement of when to prefer this over list_static_routes or other listing tools, and no prerequisites or exclusions beyond the gateway caveat.

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