Retrieve UniFi Mobility workspaces from a controller to inventory and manage workspaces across your network.
List UniFi Mobility workspaces.
| Name | Required | Description | Default |
|---|---|---|---|
| controller | No | Controller to run against (see list_controllers). Defaults to the controller chosen with select_controller, then the server default. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.6.1Does 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 implies a read-only list operation, which is useful, but does not disclose pagination, filtering, permissions, or return behavior. The existence of an output schema reduces the need to describe return values, but other behavioral details are missing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that is appropriately sized and contains no waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has one optional parameter, an output schema, and no annotations, the description is minimally adequate but not complete. It should explain when to use this tool relative to siblings or what the listing returns or scopes.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the only parameter (controller) is fully documented in the schema. The description adds no parameter semantics, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (List) and resource (UniFi Mobility workspaces), making the operation clear. It is not a tautology, but it contains no differentiation from siblings like list_mobility_devices or list_mobility_workspace_admins.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 such as list_mobility_devices or list_mobility_workspace_admins. The description gives no context, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.