Skip to main content
Glama
Sign In
UniFi MCP Server

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

update_mobility_device_wireless

Updates WiFi SSID and WPA2-PSK password settings on a UniFi Mobility device, with a dry-run option to preview changes before applying them.

Instructions

Update WiFi settings on a UniFi Mobility device.

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": {
      "workspace_id": "<workspace_id>",
      "device_id": "<device_id>",
      "ssid": "<ssid>",
      "password": "<password>"
    },
    "name": "update_mobility_device_wireless"
  }
}

Input Schema

NameRequiredDescriptionDefault
ssidYesWiFi network name (required)
confirmNoMust be true to apply the change (required unless dry_run)
dry_runNoPreview the change without applying it
passwordYesWPA2-PSK password (required)
device_idYesDevice UUID
controllerNoController to run against (see list_controllers). Defaults to the controller chosen with select_controller, then the server default.
workspace_idYesWorkspace UUID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.6.4
    • addedInput schema / properties / confirm / description
      Added value: +"Must be true to apply the change (required unless dry_run)"
    • addedInput schema / properties / device_id / description
      Added value: +"Device UUID"
    • addedInput schema / properties / dry_run / description
      Added value: +"Preview the change without applying it"
    • addedInput schema / properties / password / description
      Added value: +"WPA2-PSK password (required)"
    • addedInput schema / properties / ssid / description
      Added value: +"WiFi network name (required)"
    • addedInput schema / properties / workspace_id / description
      Added value: +"Workspace UUID"
  2. Addedv0.6.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing beyond the bare action. It omits that the change requires confirm=true (or dry_run for preview), whether applying new SSID/password disrupts connected clients, and what permissions are needed — all material for a mutation on a live wireless device.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no waste, but it is terse to the point of under-specification rather than efficient — the brevity comes at the cost of the behavioral detail this mutation tool needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and parameter documentation is complete, so the essentials for invocation are covered by structured fields. Still, a destructive-ish device mutation with no annotations leaves the description responsible for the confirm gate and side effects, which it never mentions.

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 every parameter including the confirm/dry_run gate and controller resolution is already documented in structured fields. The description adds no parameter meaning beyond the schema; 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?

States a specific verb (Update) and resource (WiFi settings on a UniFi Mobility device), which is clear enough to act on. However, it does not distinguish itself from the closely-named sibling update_mobility_device_network — an agent cannot tell from the description which of the two to use for a given settings change.

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?

No when-to-use, when-not-to-use, or alternative guidance. The nearest sibling update_mobility_device_network is never mentioned, and the two-step confirm/dry_run workflow that gates this mutation is only discoverable by reading the schema.

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

Deploy Server

Other Tools