Skip to main content
Glama

List WiFi networks

unifi_list_wlans
Read-only

List WiFi networks (SSIDs) with security, WPA mode, bands, linked network, AP groups, bandwidth and RADIUS profiles, guest/hidden flags, client isolation, MAC filtering, and enabled state.

Instructions

List WiFi networks (SSIDs) with security and WPA mode, bands, linked network, AP groups, bandwidth and RADIUS profiles, guest and hidden flags, client isolation, MAC filter and enabled state (passphrases redacted).

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

Input Schema

NameRequiredDescriptionDefault
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.
fieldsNoOnly return these fields per item (dot paths, e.g. uplink.name)
searchNoCase-insensitive substring match on names, MACs, IPs and similar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.1
    • addedInput schema / properties / fields / description
      Added value: +"Only return these fields per item (dot paths, e.g. uplink.name)"
    • addedInput schema / properties / search / description
      Added value: +"Case-insensitive substring match on names, MACs, IPs and similar"
  2. First observedv0.8.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description adds one genuinely useful behavioral fact — passphrases are redacted — but says nothing about pagination, result size, or why idempotentHint is false for a read-only list.

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?

A single front-loaded sentence with the verb first and no filler. The long field enumeration is dense but each item is informative about the payload, though it reads as a list rather than prose.

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 each returned WLAN contains (security mode, bands, AP groups, isolation, MAC filter, enabled state), which is what an agent needs to judge relevance. The omission of usage guidance is the main remaining gap.

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%, and the schema already explains raw, site, fields, and search including dot-path syntax and the unifi_list_sites cross-reference. The description adds no parameter meaning beyond it, so baseline 3 applies.

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?

Opens with a specific verb+resource ("List WiFi networks (SSIDs)") and the SSID parenthetical disambiguates it from the nearby unifi_list_networks sibling. It does not state explicitly how it differs from that sibling, so differentiation is implied rather than declared.

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

Usage Guidelines2/5

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

The description contains no when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative. An agent must infer from the name alone that this enumerates wireless networks rather than general networks.

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