Skip to main content
Glama
owine

UniFi Protect MCP

by owine
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

protect_list_fobs

Read-only

List all fobs managed by UniFi Protect, returning each fob's name, MAC address, wireless state, and button configuration.

Instructions

List all fobs managed by UniFi Protect. Returns array; each fob includes: id, modelKey, name, mac, state, awayState, buttonLabels, featureFlags (buttons[]), wirelessConnectionState (7.1.83 docs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesArray of items returned by the list endpoint

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv2.10.0
  2. Removedv2.9.0
  3. Changed4 schema fields changedv2.7.5
    • addedOutput schema / properties / result / items / properties / awayState
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Away state, e.g. \"ONLINE\""
+}
    • addedOutput schema / properties / result / items / properties / buttonLabels
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Button label preset, e.g. \"securityActions\""
+}
    • addedOutput schema / properties / result / items / properties / featureFlags
      Added value: +{
+  "description": "Feature flags (object: buttons[])"
+}
    • addedOutput schema / properties / result / items / properties / wirelessConnectionState
      Added value: +{
+  "description": "Wireless link state (object)"
+}
  4. First observedv2.7.4

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate read-only and non-destructive behavior. The description adds details about return structure (array with specific fields) and references documentation, enhancing transparency beyond annotations.

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?

Two sentences, front-loaded with purpose, then return details. Every sentence is informative with no redundancy.

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?

For a parameterless list tool with output schema, the description adequately covers what the tool returns. Missing explicit mention of output schema details, but the listed fields are sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters (empty schema), so the description naturally cannot add parameter details. With 100% schema coverage, the baseline of 4 is appropriate.

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?

The description clearly states the action ('list') and resource ('fobs managed by UniFi Protect'). It distinguishes from siblings like protect_get_fob by specifying 'list all' vs. a single fob.

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?

No explicit guidance on when to use this tool vs. alternatives. Given many list tools exist, a brief note on differentiating from other list operations would help, but the tool's simplicity makes it acceptable.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/owine/unifi-protect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server