Skip to main content
Glama
Sign In
omada-mcp

omada-mcp

by dfla-me
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get client detail

get_client
Read-only

Retrieve detailed client information by MAC address, including connection details, IP addressing, traffic stats, uptime, and lifecycle data. Useful for network diagnostics and monitoring.

Instructions

Get full detail for one client by MAC: connection (SSID, AP, channel, RSSI, SNR, rates), addressing, traffic, uptime and lifecycle.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "clientMac": "<clientMac>"
    },
    "name": "get_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientMacYesClient MAC, e.g. '5C-1B-F4-7C-25-C9'.
siteIdNoOverride the default site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint and openWorldHint, and the description adds valuable context about the return content (SSID, AP, channel, etc.), going beyond what annotations provide. No contradictions.

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?

One concise sentence that front-loads the core purpose and lists key attributes. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple get operation, annotations, and fully described parameters, the description covers all needed context, including a breakdown of what the detail includes, despite the lack of output schema.

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?

Both parameters (clientMac, siteId) have descriptions in the schema, and the tool description does not add further meaning. With 100% schema coverage, a score of 3 is appropriate.

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 explicitly states 'Get full detail for one client by MAC' and enumerates the specific details (connection, addressing, traffic, etc.), clearly distinguishing it from sibling tools like list_clients.

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 usage for a single client given a MAC address but does not explicitly contrast with list_clients or provide when-not guidance. It is adequate but lacks explicit alternative direction.

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

Deploy Server

Other Tools