Skip to main content
Glama
enuno

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_integration_wifi_broadcast

Get a single WiFi broadcast via the integration API.

Instructions

Get a single WiFi broadcast via the integration API.

Args: site_id: Site identifier broadcast_id: WiFi broadcast UUID settings: Application settings

Returns: WiFi broadcast details

Input Schema

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

Output Schema

NameRequiredDescriptionDefault

No arguments

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

B3.1/5.0
Behavior3/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. It signals a read operation and that it returns broadcast details, but says nothing about auth requirements, not-found behavior, or the 'via the integration API' constraint beyond mentioning it.

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 docstring-style Args/Returns layout is reasonably compact, but the Returns section restates what the output schema already provides, and the Args list contains a phantom parameter, so the structure includes waste and a defect.

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?

For a simple single-item read with an output schema present, the description is nearly sufficient, but the mismatched 'settings' argument and the undocumented controller parameter leave gaps against a 33% schema coverage.

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 only 33% and the description introduces a 'settings: Application settings' argument that does not exist in the schema (which has site_id, controller, broadcast_id), while never explaining the controller parameter. This is inaccurate rather than merely thin.

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?

The description states a specific verb+resource ('Get a single WiFi broadcast'), and the word 'single' implicitly distinguishes it from the list_integration_wifi_broadcasts sibling. It is clear but does not explicitly name that sibling, so it stays short of a 5.

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?

Usage is only implied by 'single' versus the obvious list sibling; there is no explicit when-to-use/when-not statement, no mention of when to prefer list_integration_wifi_broadcasts, and no prerequisites. Adequate but with clear gaps.

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