Skip to main content
Glama

UniFi Protect: Check Settings

unifi_protect_check_settings
Read-only

Audit UniFi Protect cameras and console for inconsistent settings: disabled detection, offline devices, missing footage, and storage risks. Reports issues and names the fixing tool without changing anything.

Instructions

Check every camera and the console for settings that are inconsistent, or that mean the system is not doing what someone believes it is. Finds detectors that look enabled but are gated off, cameras keeping no footage, offline devices, motion detection switched off, and storage about to stop recording. This is the tool for "are my camera settings correct" — the checks encode traps that are invisible in the Protect UI, notably a detection zone asking for an object type the device list blocks. Read-only: it reports findings and names the tool that would fix each one, and changes nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "unifi_protect_check_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Goes beyond the readOnlyHint annotation by disclosing the return shape (findings plus the name of the tool that would fix each) and by explaining the value-add: checks encode traps invisible in the Protect UI, such as a detection zone requesting an object type the device list blocks. Missing only notes on finding volume/ordering or what an empty result looks like.

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-loads the core purpose in the first sentence and each subsequent sentence adds distinct information (finding categories, usage framing, the invisible-trap rationale, read-only behavior). Slightly dense, with the second and third sentences overlapping on finding categories, but no filler.

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?

With no output schema and no parameters, the description carries the burden of explaining returns, which it does at a category level plus the fix-tool pointer. A brief note on result structure (e.g., grouped per camera, severity levels) would make it fully self-sufficient, but an agent can call it correctly as written.

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?

Zero parameters, so the schema baseline is 4; the description contributes only implied scope (all cameras plus the console, no filtering). Nothing further is needed or possible for a parameterless audit.

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 (check) and a specific resource scope (every camera and the console) for a consistency audit, and enumerates the concrete finding classes (gated detectors, cameras with no footage, offline devices, motion detection off, storage about to stop). This is clearly distinct from the sibling list/get tools, which enumerate resources rather than audit them.

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?

Explicitly frames itself as "the tool for 'are my camera settings correct'", giving a clear use trigger and implicitly steering away from per-camera getters and from unifi_protect_request for this purpose. It does not name a sibling alternative by name or state a when-not condition, which keeps it a notch below full routing guidance.

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