safe-omada-mcp

listClientsPastConnections

Retrieve historical connection data of past network clients. Filter by time range, guest status, or search by name/MAC/SSID for targeted analysis.

Instructions

Get client past connection list with historical connection data. Returns information about clients that have previously connected to the network, including connection timestamps, traffic data, duration, and device details. Supports pagination, filtering by time range and guest status, sorting by last seen time, and fuzzy search by name/MAC/SSID.

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

Input Schema

Name	Required	Description
`page`	No	Start page number. Start from 1.
`guest`	No	Filter by guest status (true/false).
`siteId`	No	Optional site ID. If not provided, uses the default site from configuration.
`timeEnd`	No	Filter by time range end timestamp (milliseconds).
`pageSize`	No	Number of entries per page. Range: 1-1000.
`searchKey`	No	Fuzzy search by name, MAC address, or SSID.
`timeStart`	No	Filter by time range start timestamp (milliseconds).
`sortLastSeen`	No	Sort by last seen time. Values: asc or desc. When multiple sorts exist, first one takes effect.
`customHeaders`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.17.0Jun 19, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description indicates a read-only operation returning historical data, but lacks details on permissions, rate limits, or side effects. With no annotations, the description carries the burden and is moderately transparent.

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?

The description is two sentences: first clarifies purpose, second lists features. Every word adds value, and the structure is efficient and front-loaded.

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 description covers key features and parameters, but lacks details about the return format or pagination behavior. Given no output schema, this is a noticeable gap for a tool with 9 parameters.

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 coverage is high (89%), so the schema already documents most parameters. The description groups features (pagination, filtering, sorting) adding some value, but does not provide deep parameter semantics beyond what the schema offers.

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 gets historical connection data for clients, using specific verbs and resources. It distinguishes itself from sibling tools like listClients (current clients) and getClientDetail (single client) by focusing on past connections.

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?

The description implies use for historical data retrieval but does not explicitly compare with alternatives or state when not to use it. An agent would infer usage from context, but explicit guidance is missing.

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

Deploy Server