UniFi MCP Server

Overview Schema Source Related Servers Discussions Admin

update_mobility_device_network

Update LAN and DHCP settings on a UniFi Mobility device, including DHCP mode, IP range, and lease time, with optional dry-run preview before applying changes.

Instructions

Update LAN / DHCP 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>"
    },
    "name": "update_mobility_device_network"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be true to apply the change (required unless dry_run)
`dry_run`	No	Preview the change without applying it
`device_id`	Yes	Device UUID
`dhcp_mode`	No	``dhcp`` to enable DHCP serving, ``none`` to disable
`controller`	No	Controller to run against (see list_controllers). Defaults to the controller chosen with select_controller, then the server default.
`host_address`	No	LAN address of the device (CIDR)
`workspace_id`	Yes	Workspace UUID
`dhcp_lease_time`	No	Lease time in seconds (0 = infinite)
`dhcp_range_stop`	No	Last address of the DHCP pool
`dhcp_range_start`	No	First address of the DHCP pool

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.6.4Oct 27, 2026
- 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 / dhcp_lease_time / description
```
Added value: +"Lease time in seconds (0 = infinite)"
```
- addedInput schema / properties / dhcp_mode / description
```
Added value: +"``dhcp`` to enable DHCP serving, ``none`` to disable"
```
- addedInput schema / properties / dhcp_range_start / description
```
Added value: +"First address of the DHCP pool"
```
- addedInput schema / properties / dhcp_range_stop / description
```
Added value: +"Last address of the DHCP pool"
```
- addedInput schema / properties / dry_run / description
```
Added value: +"Preview the change without applying it"
```
- addedInput schema / properties / host_address / description
```
Added value: +"LAN address of the device (CIDR)"
```
- addedInput schema / properties / workspace_id / description
```
Added value: +"Workspace UUID"
```
Addedv0.6.1Oct 15, 2026

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 this is an update operation but does not disclose mutation effects, confirmation requirements, dry-run behavior, reversibility, or controller selection context; the schema covers confirm/dry_run, but the description adds little behavioral transparency.

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 description is a single front-loaded sentence with no wasted words. It is appropriately concise, though its terseness leaves important context to the schema.

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?

The tool has 10 parameters, no annotations, and an output schema, so the schema and output schema carry much of the burden. The description is minimally adequate but does not explain the confirm/dry_run safety workflow or how it relates to the sibling update tools, leaving clear contextual gaps.

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 schema already documents all 10 parameters in detail. The description adds only the high-level LAN/DHCP context and no additional parameter semantics, which is the baseline when schema coverage is complete.

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 and resource: updating LAN/DHCP settings on a UniFi Mobility device. The LAN/DHCP scope implicitly distinguishes it from sibling tools such as update_mobility_device_wireless, but it does not explicitly name when to use it versus update_mobility_device.

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 gives no explicit when-to-use guidance, prerequisites, or alternatives. It only implies usage from the LAN/DHCP scope and does not mention the sibling update tools or confirm/dry_run workflow.

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

Deploy Server