Skip to main content
Glama
Sign In
UniFi MCP Server

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

update_mobility_device

Rename a UniFi Mobility device by UUID. Assign a new name of 1-32 characters, with optional dry-run preview or confirmed apply to update the label in the controller.

Instructions

Rename 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>",
      "name": "<name>"
    },
    "name": "update_mobility_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNew device name (1-32 characters, required)
confirmNoMust be true to apply the change (required unless dry_run)
dry_runNoPreview the change without applying it
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. Changed5 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 / name / description
      Added value: +"New device name (1-32 characters, 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. It says only 'Rename' and omits that the change requires confirm=true, that dry_run can preview the change, and that a controller may need to be selected — all safety-relevant for a mutation tool.

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?

The single sentence is front-loaded and free of fluff. However, for a mutation with six parameters and no annotations, such extreme brevity leaves important context unstated.

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

Completeness2/5

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

The tool has an output schema, so return values need not be described. But for a no-annotation mutation with confirm and dry_run parameters, the description is insufficient — it omits side-effect/safety behavior and controller/workspace context that an agent needs before invoking it.

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 the baseline is 3. The description adds no parameter meaning beyond 'rename' implying the name field, and does not explain workspace_id, device_id, controller, dry_run, or confirm.

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?

The description states a specific verb ('Rename') and resource ('UniFi Mobility device'), which is clearer than most sibling tools that use generic 'update' language. It does not explicitly distinguish itself from siblings like update_mobility_device_network or update_mobility_device_wireless, but the narrower 'rename' scope is evident.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no mention of the dry_run/confirm workflow. The description implies a mutation but leaves the agent to infer usage conditions entirely.

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