Skip to main content
Glama
enuno

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_all_sites_aggregated

List all sites with aggregated stats from Site Manager API.

Instructions

List all sites with aggregated stats from Site Manager API.

Args: settings: Application settings

Returns: List of sites with aggregated statistics

Input Schema

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

Output Schema

TableJSON 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.7/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, but it only names the upstream API and states the return is aggregated stats. It omits auth requirements, whether results are read-only, and any scoping/time-window behavior. Worse, its 'Args: settings' note does not correspond to any actual parameter.

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 one-sentence core is appropriately short and front-loaded, but the leftover Args/Returns boilerplate is redundant with the existing output schema and contains an inaccurate parameter name, 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.

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 value detail is not strictly required, and the purpose line plus full-coverage schema parameter are adequate to invoke the tool. The incorrect 'settings' arg reference and absence of any usage context leave it only minimally complete.

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?

Schema coverage is 100%, so the real 'controller' parameter is well documented in the schema, establishing a baseline of 3. However, the description's Args block references a nonexistent 'settings' parameter instead of 'controller', which actively misleads rather than adding value.

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 ('all sites with aggregated stats'), and the 'aggregated' qualifier distinguishes it from the plain list_sites sibling. It does not explicitly name alternatives, but the core purpose is legible.

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 when-to-use or when-not-to-use guidance is given, which is a real gap given many overlapping siblings (list_sites, get_cross_site_statistics, compare_site_performance, get_site_health_summary). The agent must guess which one fits.

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