UniFi Protect MCP

by owine

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get sensor

protect_get_sensor

Read-only

Fetch full details for a UniFi Protect sensor by ID to review state, battery, feature flags, and threshold settings.

Instructions

Get full details for a specific sensor by ID. Returns: id, modelKey, name, mac, state, type, guid, mountType, featureFlags (temperature, humidity, light, motion, waterLeak, open, tamper, smoke — each {channelCount}), batteryStatus (percentage, isLow), stats (light, humidity, temperature — each {value, status}), lightSettings / humiditySettings / temperatureSettings (isEnabled, margin, lowThreshold, highThreshold), isOpened, openStatusChangedAt, isMotionDetected, motionDetectedAt, motionSettings / glassBreakSettings (isEnabled, sensitivity, sensitivityWhenArmed), scheduleMode, armProfileIds, hasCustomSensitivityWhenArmed, alarmTriggeredAt, alarmSettings, leakDetectedAt, externalLeakDetectedAt, leakSettings (isInternalEnabled, isExternalEnabled), tamperingDetectedAt, wirelessConnectionState (signalState: signalQuality, signalStrength; batteryStatus: percentage, isLow; bridge) (7.3.70 docs).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Sensor ID

Output Schema

TableJSON 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 \| ...
`stats`	No	Environmental stats (object: light, humidity, temperature — each { value, status })
`isOpened`	No	Open/close contact state (boolean)
`modelKey`	No	Resource kind
`mountType`	No	Mount type, e.g. "door", "leak", "garage"
`featureFlags`	No	Sensor capability flags, added in 7.3.x (object: temperature, humidity, light, motion, waterLeak, open, tamper, smoke — each { channelCount })
`leakSettings`	No	Leak detection settings, read-only (object: isInternalEnabled, isExternalEnabled)
`scheduleMode`	No	Schedule mode: "always" \| "when_armed"
`alarmSettings`	No	Alarm settings (object: isEnabled)
`armProfileIds`	No	Arm profile IDs this sensor belongs to (array of strings)
`batteryStatus`	No	Battery status (object: percentage, isLow)
`lightSettings`	No	Light threshold settings (object: isEnabled, margin, lowThreshold, highThreshold)
`leakDetectedAt`	No	Last leak timestamp in epoch ms (number)
`motionSettings`	No	Motion detection settings (object: isEnabled, sensitivity, sensitivityWhenArmed)
`alarmTriggeredAt`	No	Last alarm timestamp in epoch ms (number)
`humiditySettings`	No	Humidity threshold settings (object: isEnabled, margin, lowThreshold, highThreshold)
`isMotionDetected`	No	Motion currently detected (boolean)
`motionDetectedAt`	No	Last motion timestamp in epoch ms (number)
`glassBreakSettings`	No	Glass-break detection settings (object: isEnabled, sensitivity, sensitivityWhenArmed)
`openStatusChangedAt`	No	Open-status change timestamp in epoch ms (number)
`tamperingDetectedAt`	No	Last tampering timestamp in epoch ms (number)
`temperatureSettings`	No	Temperature threshold settings (object: isEnabled, margin, lowThreshold, highThreshold)
`externalLeakDetectedAt`	No	Last external-leak timestamp in epoch ms (number)
`wirelessConnectionState`	No	Wireless link state (object: signalState { signalQuality, signalStrength }, batteryStatus { percentage, isLow }, bridge)
`hasCustomSensitivityWhenArmed`	No	Custom armed sensitivity enabled (boolean)

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 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: +{}
```

changedOutput schema / properties / glassBreakSettings / description

Previous value: -"Glass-break detection settings (object)"New value: +"Glass-break detection settings (object: isEnabled, sensitivity, sensitivityWhenArmed)"

changedOutput schema / properties / humiditySettings / description

Previous value: -"Humidity threshold settings (object)"New value: +"Humidity threshold settings (object: isEnabled, margin, lowThreshold, highThreshold)"

changedOutput schema / properties / leakSettings / description

Previous value: -"Leak detection settings (object)"New value: +"Leak detection settings, read-only (object: isInternalEnabled, isExternalEnabled)"

changedOutput schema / properties / lightSettings / description

Previous value: -"Light threshold settings (object)"New value: +"Light threshold settings (object: isEnabled, margin, lowThreshold, highThreshold)"

changedOutput schema / properties / motionSettings / description

Previous value: -"Motion detection settings (object)"New value: +"Motion detection settings (object: isEnabled, sensitivity, sensitivityWhenArmed)"

changedOutput schema / properties / stats / description

Previous value: -"Environmental stats (object: light, humidity, temperature)"New value: +"Environmental stats (object: light, humidity, temperature — each { value, status })"

changedOutput schema / properties / temperatureSettings / description

Previous value: -"Temperature threshold settings (object)"New value: +"Temperature threshold settings (object: isEnabled, margin, lowThreshold, highThreshold)"

changedOutput schema / properties / wirelessConnectionState / description

Previous value: -"Wireless link state (object: signalState, batteryStatus, bridge)"New value: +"Wireless link state (object: signalState { signalQuality, signalStrength }, batteryStatus { percentage, isLow }, bridge)"

Changed3 schema fields changedv2.13.0Sep 20, 2026

addedOutput schema / properties / featureFlags

Added value: +{
+  "description": "Sensor capability flags, added in 7.3.x (object: temperature, humidity, light, motion, waterLeak, open, tamper, smoke — each { channelCount })"
+}

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"
+  ]
+}

Changed12 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 / mountType / anyOf

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

addedOutput schema / properties / mountType / 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 / scheduleMode / anyOf

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

addedOutput schema / properties / scheduleMode / 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"
+]
```

Changed22 schema fields changedv2.7.5Jun 21, 2026

addedOutput schema / properties / alarmSettings

Added value: +{
+  "description": "Alarm settings (object: isEnabled)"
+}

addedOutput schema / properties / alarmTriggeredAt

Added value: +{
+  "description": "Last alarm timestamp in epoch ms (number)"
+}

addedOutput schema / properties / armProfileIds

Added value: +{
+  "description": "Arm profile IDs this sensor belongs to (array of strings)"
+}

addedOutput schema / properties / batteryStatus

Added value: +{
+  "description": "Battery status (object: percentage, isLow)"
+}

addedOutput schema / properties / externalLeakDetectedAt

Added value: +{
+  "description": "Last external-leak timestamp in epoch ms (number)"
+}

addedOutput schema / properties / glassBreakSettings

Added value: +{
+  "description": "Glass-break detection settings (object)"
+}

addedOutput schema / properties / hasCustomSensitivityWhenArmed

Added value: +{
+  "description": "Custom armed sensitivity enabled (boolean)"
+}

addedOutput schema / properties / humiditySettings

Added value: +{
+  "description": "Humidity threshold settings (object)"
+}

addedOutput schema / properties / isMotionDetected

Added value: +{
+  "description": "Motion currently detected (boolean)"
+}

addedOutput schema / properties / isOpened

Added value: +{
+  "description": "Open/close contact state (boolean)"
+}

addedOutput schema / properties / leakDetectedAt

Added value: +{
+  "description": "Last leak timestamp in epoch ms (number)"
+}

addedOutput schema / properties / leakSettings

Added value: +{
+  "description": "Leak detection settings (object)"
+}

addedOutput schema / properties / lightSettings

Added value: +{
+  "description": "Light threshold settings (object)"
+}

addedOutput schema / properties / motionDetectedAt

Added value: +{
+  "description": "Last motion timestamp in epoch ms (number)"
+}

addedOutput schema / properties / motionSettings

Added value: +{
+  "description": "Motion detection settings (object)"
+}

addedOutput schema / properties / mountType

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Mount type, e.g. \"door\", \"leak\", \"garage\""
+}

addedOutput schema / properties / openStatusChangedAt

Added value: +{
+  "description": "Open-status change timestamp in epoch ms (number)"
+}

addedOutput schema / properties / scheduleMode

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Schedule mode: \"always\" | \"when_armed\""
+}

addedOutput schema / properties / stats

Added value: +{
+  "description": "Environmental stats (object: light, humidity, temperature)"
+}

addedOutput schema / properties / tamperingDetectedAt

Added value: +{
+  "description": "Last tampering timestamp in epoch ms (number)"
+}

addedOutput schema / properties / temperatureSettings

Added value: +{
+  "description": "Temperature threshold settings (object)"
+}

addedOutput schema / properties / wirelessConnectionState

Added value: +{
+  "description": "Wireless link state (object: signalState, batteryStatus, bridge)"
+}

First observedv2.7.4Jun 11, 2026

TDQS

C2.8/5.0

Behavior2/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 covered. The description adds no behavioral context beyond that — no auth requirements, no rate limits, no error or not-found semantics — and instead spends its budget restating return fields.

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

Conciseness2/5

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

The first sentence is a well-formed, front-loaded purpose statement, but everything after it is a sprawling enumeration of return fields. Since an output schema exists, that enumeration is largely redundant and dominates the description's length.

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 single-parameter read tool with a full output schema and safety annotations, the core need is covered by the first sentence. The remaining text re-describes the return payload the output schema already defines, so the description is verbose in the wrong place and silent on genuinely useful details like not-found behavior.

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 100% schema description coverage and a single parameter fully documented as 'Sensor ID' with a pattern, the schema carries the meaning and the baseline is 3. The phrase 'by ID' adds nothing about format or sourcing of the ID beyond what the schema already specifies.

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 opening sentence states a specific verb (Get), resource (sensor), and scope (by ID, full details), which distinguishes it from the sibling protect_list_sensors in practice. It never names the sibling or any alternative explicitly, but the get-vs-list distinction is implicit in 'by ID'.

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?

There is no guidance on when to use this tool versus protect_list_sensors or the other protect_get_* siblings, no prerequisite for obtaining a valid sensor ID, and no error behavior for unknown IDs. The description only says what it returns, not when to reach for it.

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