UniFi Protect MCP

by owine

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get chime

protect_get_chime

Read-only

Retrieve complete details for a specific chime by ID, including model, state, MAC, linked cameras, and ring settings.

Instructions

Get full details for a specific chime by ID. Returns: id, modelKey, name, mac, state, type, guid, cameraIds (array of camera IDs), ringSettings (array of objects: cameraId, volume, ringtoneId, repeatTimes) — verified live 7.3.70.

Input Schema

Name	Required	Description	Default
`id`	Yes	Chime ID

Output Schema

Name	Required	Description
`id`	No	Device ID
`mac`	No	MAC address
`guid`	No	Hardware MODEL GUID, shared by every unit of the same model. NOT a per-device identifier — use `id` to identify a device.
`name`	No	Device name
`type`	No	Hardware model name, e.g. "UVC G6 Turret", "UP Chime PoE", "UNVR-PRO"
`state`	No	CONNECTED \| DISCONNECTED \| ...
`modelKey`	No	Resource kind
`cameraIds`	No	Paired camera IDs (array of strings)
`ringSettings`	No	Per-camera ring config (array of objects: cameraId, volume, ringtoneId, repeatTimes)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.15.0Oct 14, 2026
- addedInput schema / properties / id / pattern
```
Added value: +"^[A-Za-z0-9_-]{1,64}$"
```
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

Changed2 schema fields changedv2.13.0Sep 20, 2026

addedOutput schema / properties / guid

Added value: +{
+  "description": "Hardware MODEL GUID, shared by every unit of the same model. NOT a per-device identifier — use `id` to identify a device.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / type

Added value: +{
+  "description": "Hardware model name, e.g. \"UVC G6 Turret\", \"UP Chime PoE\", \"UNVR-PRO\"",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed8 schema fields changedv2.11.5Sep 13, 2026

removedOutput schema / properties / mac / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / mac / type

Added value: +[
+  "string",
+  "null"
+]

removedOutput schema / properties / modelKey / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / modelKey / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / state / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / state / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed2 schema fields changedv2.7.5Jun 21, 2026

addedOutput schema / properties / cameraIds

Added value: +{
+  "description": "Paired camera IDs (array of strings)"
+}

addedOutput schema / properties / ringSettings

Added value: +{
+  "description": "Per-camera ring config (array of objects: cameraId, volume, ringtoneId, repeatTimes)"
+}

First observedv2.7.4Jun 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description contributes the field inventory and a version-verification note, which is beyond the annotations, but it says nothing about error behavior for unknown IDs or pagination (none expected).

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?

Front-loaded with the purpose in the first clause, then the return fields. The long field enumeration is somewhat bloated given an output schema exists, but nothing is misleading or wasted.

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?

The description is sufficient for a single-parameter read tool whose annotations carry the safety profile and whose output schema carries the return shape. The return-field list duplicates the output schema rather than filling a gap, but no information an agent needs to invoke it is missing.

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?

With one parameter and 100% schema description coverage, the schema already documents the 'id' field and its pattern. The description adds no syntax, format, or sourcing guidance beyond restating that lookup is by ID, so the baseline of 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 full details for a specific chime by ID'), which cleanly separates it from the list-style siblings like protect_list_chimes. It does not name a sibling explicitly, but 'by ID' makes the selection unambiguous.

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: the phrase 'by ID' signals that a chime identifier is required, which an agent must obtain from protect_list_chimes first. No explicit when-to-use, prerequisite, or when-not guidance is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.