omada-mcp

by falehsub

Overview Schema Source Related Servers Discussions Admin

Python

Remote

List wired clients

list_wired_clients

Read-onlyIdempotent

List only wired clients, same fields as list_clients.

Instructions

List only wired clients, same fields as list_clients.

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

Input Schema

Name	Required	Description	Default
`site`	No
`limit`	No	Max clients (1-5000, default 500)

Output Schema

Name	Required	Description	Default
`count`	Yes
`items`	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 needs no restatement. The description adds one useful behavioral fact — the response shape matches list_clients — but says nothing about pagination behavior despite the limit parameter capping at 5000.

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 short sentence with the filtering constraint front-loaded and no wasted words. It is efficient, though bordering on under-specification given the tool takes two parameters.

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 annotations cover the safety profile. What remains missing is the meaning of the site parameter and any pagination guidance, which leaves the definition only minimally sufficient for a two-parameter list tool.

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 coverage is 50%: limit is documented in the schema, but site has no description anywhere. The description adds no parameter meaning at all — no hint about what site accepts (name vs. ID) or how limit interacts with the default of 500 — so it fails to compensate for the undocumented half.

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 and resource ('List ... wired clients') and scopes it to a single client type, which implicitly separates it from list_clients and list_wifi_clients. It stops short of naming those siblings explicitly, so the differentiation is inferred 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?

'List only wired clients' implies the selection condition (use when you need wired-only results) and the 'same fields as list_clients' note hints that list_clients is the unfiltered superset. There is no explicit when-not-to-use statement or named alternative, so the routing guidance is only implied.

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