Skip to main content
Glama
enuno

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_hosts

List all managed hosts/consoles.

Instructions

List all managed hosts/consoles.

Args: settings: Application settings limit: Optional maximum number of hosts to return offset: Optional number of hosts to skip (for pagination)

Returns: List of managed hosts

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
controllerNoController to run against (see list_controllers). Defaults to the controller chosen with select_controller, then the server default.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / controller
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Controller to run against (see list_controllers). Defaults to the controller chosen with select_controller, then the server default."
+}
  2. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses only that limit/offset paginate. It says nothing about the read-only nature, permissions, cross-controller scope, or what 'managed' means. Worse, it introduces a parameter ('settings') that the schema does not contain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in a single clean sentence, but the Args/Returns block largely restates schema fields and includes a phantom 'settings' entry, so not every line earns its place.

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?

An output schema exists, so the 'Returns' line is redundant, and the description omits the controller-targeting behavior entirely while listing a nonexistent parameter. For a list tool that can run against multiple controllers, that omission leaves a real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description documents limit and offset (already inferable from schema) but misnames a parameter as 'settings: Application settings' that does not exist in the schema, and entirely omits the 'controller' parameter — the one parameter that actually has a schema description and matters for execution. This is inaccurate rather than additive.

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 clear verb+resource ('List all managed hosts/consoles'), so an agent knows this is an enumeration tool. However it conflates two concepts ('hosts/consoles') and does nothing to distinguish itself from siblings such as get_host, list_controllers, or list_integration_devices, so the reader must infer scope from the rest of the catalog.

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 when-to-use guidance, no conditions, and no named alternatives. Given the very dense sibling set (list_controllers, get_active_controller, list_integration_devices, etc.), the agent gets no help deciding when list_hosts is the right call.

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