UniFi Internal API MCP Server

list_wlan_conf

Retrieve UniFi WLAN configurations to inspect wireless network settings, or get a specific WLAN by its ID.

Instructions

List WLAN configurations (wireless networks), or get a specific WLAN by ID.

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

Input Schema

Name	Required	Description	Default
`wlan_id`	No	Optional WLAN _id to fetch a specific WLAN

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It clearly implies a read-only operation ('List') and an optional filter, but it does not disclose any additional behavioral traits such as pagination, authentication requirements, or response details. This is adequate for a benign list tool but lacks extra context that could be useful.

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?

The description is a single, efficient sentence that front-loads the main action and adds the optional ID variant using an 'or' clause. Every word earns its place.

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?

Given the low complexity (one optional parameter, no required fields, output schema provided), the description is nearly complete. It only misses a brief positioning note about related tools like list_wlan_groups, and does not clarify whether additional filters or pagination are supported, leaving a minor context 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 coverage is 100% (the only parameter has a full description), so the baseline is 3. The description's 'get a specific WLAN by ID' adds no new meaning beyond the schema's own parameter description, which already explains the optional ID.

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's function: 'List WLAN configurations (wireless networks), or get a specific WLAN by ID.' It uses a specific verb ('List') and resource ('WLAN configurations'), and distinguishes itself from sibling tools like list_wlan_groups by focusing on configurations rather than groups.

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?

The optional ID parameter implies when to use the tool (list all vs. get specific), but no explicit guidance is given about when to choose this over alternatives like list_wlan_groups or list_networks. There are no exclusions or alternative recommendations.

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

Deploy Server