Skip to main content
Glama

Get RF scan results

unifi_get_rf_scan
Read-only

Retrieve an access point's last RF spectrum scan to check if a scan is running, when it last ran, and per-channel utilization and interference. Returns no results if no scan exists.

Instructions

Get an access point's last RF/spectrum scan: whether a scan is running, when it last ran, and utilization and interference per channel. Returns scanning: false and no results if the AP has no scan.

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_rf_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
macYesMAC address of the access point
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

A3.9/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 real behavioral value beyond that: it discloses the edge case that a missing scan yields 'scanning: false and no results', which prevents an agent from misreading an empty response as an error.

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 the resource and its contents, followed immediately by the failure/empty case. No filler or restatement of the title.

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?

With no output schema, the description carries the burden and does so: it lists the returned dimensions and explains the no-result behavior. Combined with 100%-covered parameters, an agent has everything needed to call and interpret this tool.

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 100% and both parameters are documented in-schema, including the 'site' default and the pointer to unifi_list_sites. The description only implicitly refers to the AP via 'an access point's ... scan' and adds no format guidance for the MAC beyond what the schema states.

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

Purpose4/5

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

The description names a specific verb and resource ('Get an access point's last RF/spectrum scan') and enumerates the contents (scan status, last-run time, per-channel utilization and interference). It is clearly distinct from generic device lookups in the sibling list, though it never explicitly names an alternative such as unifi_get_device.

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?

Usage is only implied: an agent can infer that this is the tool for inspecting an AP's radio environment. There is no explicit statement of when to prefer it over device-level tools or what prerequisites (AP reachable, scan previously run) apply, aside from the no-scan case.

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