Skip to main content
Glama

List neighbouring/rogue APs

unifi_list_rogue_aps
Read-only

List nearby and rogue access points your UniFi APs can hear, strongest first, with SSID, BSSID, channel, band, signal, security, vendor, and last-seen details from the past 24 hours by default.

Instructions

List access points your APs can hear (neighbours and ones flagged as rogue), strongest first (default seen in the last 24 hours): SSID, BSSID, channel, band, signal, security, vendor, which of your APs saw it and when. For per-channel interference use unifi_get_rf_scan.

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

Input Schema

NameRequiredDescriptionDefault
siteNoSite name/ID as used in the API (e.g. 'default'). Defaults to the configured site. See unifi_list_sites.
hoursNoSeen within this many hours (default 24; fractions are rounded up to whole hours)
limitNoMaximum items to return (default 100)
fieldsNoOnly return these fields per item (dot paths, e.g. uplink.name)
searchNoCase-insensitive substring match on names, MACs, IPs and similar
rogue_onlyNoOnly APs flagged as rogue

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.9.1
    • addedInput schema / properties / fields / description
      Added value: +"Only return these fields per item (dot paths, e.g. uplink.name)"
    • changedInput schema / properties / hours / description
      Previous value: -"Seen within this many hours (default 24)"New value: +"Seen within this many hours (default 24; fractions are rounded up to whole hours)"
    • removedInput schema / properties / hours / maximum
      Removed value: -9007199254740991
    • changedInput schema / properties / hours / type
      Previous value: -"integer"New value: +"number"
    • changedInput schema / properties / limit / description
      Previous value: -"Default 100"New value: +"Maximum items to return (default 100)"
    • addedInput schema / properties / search / description
      Added value: +"Case-insensitive substring match on names, MACs, IPs and similar"
  2. First observedv0.8.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds value beyond them: causal scope ('your APs can hear'), deterministic ordering ('strongest first'), a default 24-hour window, and the exact fields returned. Only pagination/limit behaviour and any known freshness caveats are left unstated.

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?

A single front-loaded sentence, a compact parenthetical for the default window, a field list, and one routing sentence. No redundant restatement of the title or name.

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 compensates by naming the returned fields (SSID, BSSID, channel, band, signal, security, vendor, observer, timestamp). Combined with annotations and full schema coverage, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so most parameter meaning is already structured. The description still contributes by restating the 24-hour default for the time window and by enumerating the returned fields, which implicitly explains what 'fields' projects over.

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?

States a specific verb and resource ('List access points your APs can hear') plus the scope nuance (neighbours and rogue-flagged), which distinguishes it from unifi_get_rf_scan and from the device/client list siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to an alternative with a condition: 'For per-channel interference use unifi_get_rf_scan.' The default time window and the rogue vs neighbour distinction also frame when this tool is the right choice.

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