Skip to main content
Glama
Sign In
unifi-mcp-server

unifi-mcp-server

by us-all
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list-hosts

Read-only

Retrieve a list of all UniFi console hosts including UDM, UDM Pro, and Cloud Key.

Instructions

List all UniFi console hosts (UDM, UDM Pro, Cloud Key, etc.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-hosts"
  }
}

Input Schema

NameRequiredDescriptionDefault
extractFieldsNoComma-separated dotted paths to project from response (e.g. 'id,name,owner.name,columns.*.name'). Use `*` as wildcard for arrays/objects. Wrap field names with dots in backticks. Reduces response tokens dramatically on large entities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.4
  2. Removedv1.12.3
  3. First observedv1.11.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds that it lists all hosts, which is consistent. No hidden side effects disclosed, but also no contradictions.

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

Conciseness5/5

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

The description is a single sentence that is front-loaded with the core action and resource, and every word is meaningful with no waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with one optional parameter and no output schema, the description provides sufficient information. The openWorldHint signals possible large result sets, but no pagination details are needed given the optional extractFields param can reduce tokens.

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?

The single parameter 'extractFields' has 100% schema coverage with a detailed description. The tool description does not add additional meaning beyond the schema, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'list' and resource 'UniFi console hosts', with examples (UDM, UDM Pro, Cloud Key) that distinguish it from siblings like 'get-host' (singular) and other device/site tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not-to-use guidance is provided. The description implies a broad listing, but does not contrast with 'get-host' for specific host details or mention prerequisites.

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