Skip to main content
Glama
Sign In
UniFi MCP

UniFi MCP

by frousselet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

protect_get_camera

Get detailed information about a specific UniFi Protect camera by providing its camera ID.

Instructions

Get detailed information about a specific Protect camera.

Args: camera_id: The camera ID (get from protect_list_cameras).

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

Input Schema

NameRequiredDescriptionDefault
camera_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It correctly indicates a read operation ('Get'), but does not elaborate on authorization, rate limits, or the exact scope of 'detailed information.' This is adequate for a simple getter but lacks deeper context.

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 extremely concise: two short sentences. The first states the purpose, the second documents the parameter. There is no redundant information, and all content is necessary.

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?

Given that an output schema exists (so return values are documented there), and the tool has only one required parameter, the description is complete. It covers what the tool does and how to get the input, meeting all needs for correct invocation.

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?

The input schema has 0% description coverage, but the description adds meaningful context: 'camera_id: The camera ID (get from protect_list_cameras).' This tells the agent where to source the value, which significantly aids correct usage.

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 tool's purpose: 'Get detailed information about a specific Protect camera.' It specifies the resource (camera) and indicates it returns detailed info, distinguishing it from listing or updating tools.

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 description advises that the camera_id should be obtained from protect_list_cameras, providing clear context for usage. However, it does not explicitly state when not to use this tool or list alternatives beyond the implied order of operations.

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