Skip to main content
Glama
Sign In
UniFi MCP

UniFi MCP

by frousselet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

protect_get_camera_snapshot

Retrieve a JPEG snapshot from a UniFi Protect camera by providing the camera ID. The snapshot is returned as a base64-encoded image.

Instructions

Get a JPEG snapshot from a Protect camera.

Returns the snapshot as a base64-encoded JPEG image.

Args: camera_id: The camera ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "camera_id": "<camera_id>"
    },
    "name": "protect_get_camera_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
camera_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that the output is a base64-encoded JPEG image, which is useful. However, it does not mention potential failure modes, permissions required, or any side effects, leaving gaps in transparency.

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?

The description is very concise with three short sentences: one stating the purpose, one describing the output format, and one explaining the parameter. No extra information, and it is front-loaded with the main action.

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?

Given the tool's simplicity (one parameter, clear output), the description is adequately complete. It covers the input and output format. However, it lacks error handling context or prerequisites (e.g., camera must be online) that could be helpful.

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?

Schema coverage is 0%, but the description includes an 'Args' section explaining the camera_id parameter as 'The camera ID.' This adds meaning beyond the schema's property name. It is clear and concise, though it could specify the expected format of the ID.

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 ('Get') and the specific resource ('a JPEG snapshot from a Protect camera'). It distinguishes itself from sibling tools like protect_list_cameras and protect_get_camera by specifying the snapshot retrieval.

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?

The description provides no guidance on when to use this tool vs alternatives. It does not mention prerequisites, limitations, or scenarios where other tools would be more appropriate. Usage is only implied by the tool's name and purpose.

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