Skip to main content
Glama
Sign In
UniFi MCP Server

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_innerspace_inventory

Lists unplaced devices in InnerSpace inventory for a specified console, helping you identify hardware not yet assigned to a site.

Instructions

List unplaced devices in InnerSpace inventory 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_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. Changed1 schema field changedv0.6.4
    • addedInput schema / properties / console_id / description
      Added value: +"Cloud Connector console UUID (from ``list_hosts``)"
  2. Addedv0.6.1

TDQS

B3.2/5.0
Behavior3/5

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

With zero annotations the description must carry the behavioral burden. 'List' and the 'unplaced' qualifier imply a safe read that returns devices not yet placed on a floor plan, which is useful scope information. But it says nothing about read-only safety, permissions, pagination, or result size, leaving real gaps for a mutation-free inventory call.

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 front-loaded sentence with zero waste. It is perhaps slightly too terse given the available space, and 'on a console' is a bit ambiguous, but nothing in it is filler.

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 and full parameter documentation cover the return shape and arguments, so the description only needs to add usage and behavioral context. It gives a useful scope hint ('unplaced') but omits when to use it versus sibling InnerSpace tools and any operational caveats, leaving it barely adequate rather than complete.

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 coverage is 100%: console_id's link to list_hosts and the controller's default/select_controller chain are already fully documented in the schema. The description adds no parameter-level meaning beyond what the schema provides, so the 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 (list) and resource (InnerSpace inventory devices), plus the qualifier 'unplaced' and the console scope. That qualifier distinguishes it from sibling listers such as list_innerspace_access_points and list_innerspace_switches, though no sibling is named explicitly.

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 choose this over the other InnerSpace listers (access points, floor plans, switches) or over get_innerspace_project. The only implicit signal is the 'unplaced' qualifier. No exclusions, prerequisites, or alternatives are given.

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