Skip to main content
Glama
Sign In
UniFi MCP Server

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_innerspace_switches

List switches placed on InnerSpace floor plans for a console, optionally filtered by site, to identify device locations and layout.

Instructions

List switches placed on InnerSpace floor plans on a console.

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": {
      "console_id": "<console_id>"
    },
    "name": "list_innerspace_switches"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoOptional site UUID to filter switches by site
console_idYesCloud Connector console UUID (from ``list_hosts``)
controllerNoController to run against (see list_controllers). Defaults to the controller chosen with select_controller, then the server default.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.4
    • addedInput schema / properties / console_id / description
      Added value: +"Cloud Connector console UUID (from ``list_hosts``)"
    • addedInput schema / properties / site_id / description
      Added value: +"Optional site UUID to filter switches by site"
  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 burden. 'List' implies read-only, but nothing is said about pagination, permissions, scoping behavior when site_id is omitted, or which controller actually services the request beyond what the schema notes.

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?

A single well-formed sentence with no wasted words. It is front-loaded on the resource, though it is arguably too thin given the tool's dependency structure.

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 so return values need no explanation, and the schema fully documents parameters. However, for a cross-system list tool with controller/site/console layering, the description does not clarify filtering or default behavior, leaving 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 all three parameters (site_id, console_id, controller) are already documented with defaults and cross-references. The description's 'on a console' only echoes the required console_id, adding no new semantics.

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 and resource ('List switches placed on InnerSpace floor plans on a console'), which is clearly a read of switch entities. It does not distinguish itself from close siblings such as list_innerspace_access_points, list_innerspace_inventory, or list_innerspace_floor_plans, which an agent could easily confuse.

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 guidance on when to use this versus the other InnerSpace list tools, nor any prerequisites. The only usage signal is the implicit dependency on a console (console_id), which the schema already encodes.

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