safe-omada-mcp

listClientsActivity

Retrieve time-series client activity statistics showing new, active, and disconnected clients for both wireless and wired devices to monitor connection trends.

Instructions

Get client activity statistics over time from the dashboard. Returns time-series data showing new, active, and disconnected clients (both wireless/EAP and wired/switch) for each time snapshot. Useful for monitoring client connection trends and activity patterns.

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

Input Schema

Name	Required	Description
`end`	No	Optional end timestamp in seconds (e.g., 1682000000)
`start`	No	Optional start timestamp in seconds (e.g., 1682000000)
`siteId`	No	Optional site ID. If not provided, uses the default site from configuration.
`customHeaders`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.17.0Jun 19, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the type of data (time-series) and client categories, but does not mention behavioral traits like data aggregation intervals, real-time vs historical, or authentication requirements. Adequate but not thorough.

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

Conciseness5/5

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

Two sentences efficiently convey purpose and return type, with no redundant information. The first sentence is action-oriented, and the second adds context.

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?

Given no output schema, the description is brief for a time-series tool. It lacks details on the response structure, pagination, or how snapshots are timestamped. While it covers essential data points, more completeness would aid agent usage.

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

Parameters3/5

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

Schema provides descriptions for 3 of 4 parameters (75% coverage). The description mentions 'over time' correlating with start/end but adds no further meaning. customHeaders parameter is undocumented in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves client activity statistics as time-series data, specifying new, active, and disconnected clients for both wireless and wired types. This differentiates it from sibling tools like listClients or getClientDetail.

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?

The description notes it is 'useful for monitoring client connection trends and activity patterns', implicitly guiding when to use. However, it does not explicitly state when not to use or mention alternatives among the many sibling tools.

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

Deploy Server