Skip to main content
Glama
Sign In
omada-mcp

omada-mcp

by dfla-me
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get device detail

get_device
Read-only

Retrieve detailed information for a single network device using its MAC address. For APs, includes per-band radio configuration such as channel, width, and transmit power.

Instructions

Get detail for one device by MAC. For APs, also includes per-band radio config (channel, width, Tx power). Use list_devices to find MACs.

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": {
      "deviceMac": "<deviceMac>"
    },
    "name": "get_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceMacYesMAC, e.g. 'A8-29-48-C1-BB-C0'.
siteIdNoOverride the default site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint. Description adds that for APs, the response includes radio config details, which goes beyond annotations. 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?

Two sentences, front-loaded with core purpose, and efficient. No redundant information.

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

Completeness4/5

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

Sufficient for a simple read tool with annotations. Covers key output for APs and directs to sibling for finding MACs. Could mention error cases, but overall adequate.

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?

Input schema has 100% description coverage with clear parameter descriptions. The tool description does not add additional parameter details beyond the schema, but provides context on output behavior for APs.

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 details for one device by MAC, with specific mention of per-band radio config for APs, distinguishing it from siblings like list_devices.

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?

Explicitly suggests using list_devices to find MACs, providing clear guidance. Does not explicitly list when not to use, but the context of siblings implies appropriate use cases.

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