Skip to main content
Glama

List RADIUS profiles

unifi_list_radius_profiles
Read-only

Lists RADIUS profiles used by WPA-Enterprise WiFi, 802.1X switch ports, and L2TP VPN so you can identify available authentication configurations, with secrets redacted.

Instructions

List RADIUS profiles used by WPA-Enterprise WiFi, 802.1X switch ports and L2TP VPN (secrets 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_radius_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, non-open-world behavior, so the bar is lower. The parenthetical '(secrets redacted)' is a genuinely useful disclosure beyond the annotations: the agent learns the credentials will be masked and must not expect to retrieve usable RADIUS secrets. Return size or pagination behavior is still 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 with zero filler that conveys resource, consumption context and the redaction caveat. Nothing could be removed without losing information.

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?

For a three-optional-parameter read-only list tool with no output schema, the definition covers what the resource is and the key return caveat (redacted secrets). The remaining gap is cardinality/pagination expectations, which an agent enumerating profiles might want.

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 all three parameters (site, fields, search) are already documented with examples, and the baseline of 3 applies. The description adds no further meaning about these parameters, offering neither default behavior details nor interaction between search and fields.

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?

Specific verb ('List') plus a precise resource ('RADIUS profiles') and an explicit scope note that these are the profiles consumed by WPA-Enterprise WiFi, 802.1X switch ports and L2TP VPN. That scope distinguishes it in practice from the sibling unifi_list_radius_accounts, though the description never names that sibling to make the boundary explicit.

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 use context (WiFi/802.1X/VPN authentication) implies when an agent would reach for this tool, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as the RADIUS accounts listing. Guidance is inferable rather than stated.

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