Skip to main content
Glama
owine

UniFi Protect MCP

by owine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

protect_get_bridge

Read-only

Fetch complete bridge information by ID, including MAC address, state, type, platform, and connected client list.

Instructions

Get full details for a specific bridge by ID. Returns: id, modelKey, name, mac, state, type, guid, platform, clients (array of MACs), maxClients (7.3.47 docs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesBridge ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoDevice ID
macNoMAC address
guidNoHardware MODEL GUID, shared by every unit of the same model. NOT a per-device identifier — use `id` to identify a device.
nameNoDevice name
typeNoHardware model name, e.g. "UVC G6 Turret", "UP Chime PoE", "UNVR-PRO"
stateNoCONNECTED | DISCONNECTED | ...
clientsNoConnected client MACs (array of strings)
modelKeyNoResource kind
platformNoHardware platform, e.g. "mt7621"
maxClientsNoMax client capacity (number)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.13.0
    • 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"
+  ]
+}
  2. Changed10 schema fields changedv2.11.5
    • 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 / platform / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / platform / 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"
+]
  3. Changed3 schema fields changedv2.7.5
    • addedOutput schema / properties / clients
      Added value: +{
+  "description": "Connected client MACs (array of strings)"
+}
    • addedOutput schema / properties / maxClients
      Added value: +{
+  "description": "Max client capacity (number)"
+}
    • addedOutput schema / properties / platform
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Hardware platform, e.g. \"mt7621\""
+}
  4. First observedv2.7.4

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by enumerating the exact returned fields, including the clients array and the maxClients version note, which the annotations do not convey.

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

Conciseness5/5

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

A single, front-loaded sentence states the action, then lists return fields in a compact colon-delimited format. Every word earns its place; no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity get-by-id tool with one documented parameter, read-only annotations, and an output schema, the description is complete. It even adds the returned-field list, which exceeds what the structured fields require.

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?

The schema already describes 'id' as 'Bridge ID' (100% coverage), so the baseline is 3. The description reinforces that the ID identifies a specific bridge but adds no format, source, or usage details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get'), a precise resource ('full details for a specific bridge by ID'), and clearly distinguishes itself from list_bridges and other get_* siblings. The returned-field list further clarifies the tool's scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'by ID' makes it clear this is for retrieving one specific bridge, not enumerating bridges (which list_bridges handles). It does not explicitly name alternative tools or exclusion conditions, but the context is unambiguous for a get-by-id tool.

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