Skip to main content
Glama

Get device details

unifi_get_device
Read-only

Retrieve a UniFi device by MAC to inspect its serial, ports, radio settings, statistics, PoE use, WAN links, and LED settings. Returns an error if no device matches the MAC.

Instructions

Get one device by MAC: its list summary plus serial, ports, radio settings and stats, outlets, WAN links, system stats, load average, PoE use and LED settings. Errors if no device has that MAC. For a switch's ports with LLDP neighbours and profile names use unifi_list_switch_ports.

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": {
      "mac": "<mac>"
    },
    "name": "unifi_get_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
macYesMAC address, e.g. aa:bb:cc:dd:ee:ff
rawNoReturn the full controller objects (large)
siteNoSite name/ID as used in the API (e.g. 'default'). Defaults to the configured site. See unifi_list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds the failure mode ('Errors if no device has that MAC') and signals a heavy payload by describing the full field list. It does not discuss pagination or response shape, but for a single-object read that gap is minor.

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?

The key identification ('one device by MAC') is front-loaded, followed by the return payload, the error condition, and the sibling pointer. The long noun list of returned fields is dense but each item is informative; nothing is redundant filler.

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?

With no output schema, the description usefully enumerates what comes back and names the error case, which is what an agent needs before calling. The only omission is any note about the size tradeoff of raw, which the schema already flags as 'large'.

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 description coverage is 100%, so the MAC format, the raw flag's payload cost, and the site lookup with a pointer to unifi_list_sites are all already documented structurally. The description reinforces MAC as the key but adds no new meaning for raw or site, which is the baseline-3 case.

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 opens with a specific verb and resource ('Get one device by MAC') and enumerates the exact data returned: serial, ports, radio settings, stats, outlets, WAN links, load average, PoE and LED settings. That is enough to distinguish it from unifi_list_devices (many devices) and unifi_list_switch_ports (port-specific view) without opening a schema.

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?

It states the selection condition precisely ('by MAC') and routes the agent to unifi_list_switch_ports when LLDP neighbours and profile names are wanted instead. It does not explicitly say how to find a MAC or point at unifi_list_devices for enumeration, but the alternative guidance is concrete enough to act on.

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