Skip to main content
Glama
Sign In
UniFi MCP Server

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_integration_device

Retrieve one adopted UniFi device by site ID and device UUID through the integration API to inspect its details.

Instructions

Get a single adopted device via the integration API.

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": {
      "site_id": "<site_id>",
      "device_id": "<device_id>"
    },
    "name": "get_integration_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesSite identifier
device_idYesDevice UUID
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. Changed2 schema fields changedv0.6.4
    • addedInput schema / properties / device_id / description
      Added value: +"Device UUID"
    • addedInput schema / properties / site_id / description
      Added value: +"Site identifier"
  2. 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."
+}
  3. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations, so the description carries the full burden, and it discloses almost nothing behavioral: not that it is a read-only operation, not what happens if the device is not adopted or does not exist, not auth/permission requirements. The word 'adopted' is the only real semantic signal about preconditions.

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 padding. It is efficient, though the terseness contributes to the gaps in usage and behavior rather than being purely virtuous.

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 values need no explanation, and all three parameters are documented in the schema. What is missing is the behavioral and selection context an agent needs (read-only nature, error/not-found handling, when to prefer this over get_mobility_device) given there are no annotations.

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 description coverage is 100%, and the schema already explains site_id, device_id, and the controller fallback chain. The description adds no parameter meaning beyond that, so 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 and resource ('Get a single adopted device') and the qualifier 'via the integration API' distinguishes it from get_mobility_device and the connector_* family. It does not explicitly name list_integration_devices, but 'single' versus 'list' makes the split inferable.

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 statement of when to use this over get_mobility_device, list_integration_devices, or list_integration_devices-by-tag. The only guidance is implicit in the word 'single'; no prerequisites or exclusions 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