Skip to main content
Glama
owine

UniFi Protect MCP

by owine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get RTSP streams

protect_get_rtsp_streams
Read-only

Retrieve active RTSPS stream sessions for a camera, returning high, medium, low, and package URLs or null. Use protect_create_rtsp_stream to start a session.

Instructions

Get active RTSPS stream sessions for a camera. Returns: high, medium, low, package — each an rtsps:// URL, or null (or absent) when no session is active at that quality. Use protect_create_rtsp_stream to start one. Each URL is a bearer credential for live video: do not repeat it unless the user asked for it.

Input Schema

NameRequiredDescriptionDefault
idYesCamera ID

Output Schema

NameRequiredDescriptionDefault
lowNoRTSPS URL for the low-quality stream
highNoRTSPS URL for the high-quality stream
mediumNoRTSPS URL for the medium-quality stream
packageNoRTSPS URL for the package-camera stream

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.15.0
    • addedInput schema / properties / id / pattern
      Added value: +"^[A-Za-z0-9_-]{1,64}$"
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
  2. Changed8 schema fields changedv2.11.5
    • removedOutput schema / properties / high / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / high / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / low / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / low / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / medium / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / medium / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / package / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / package / type
      Added value: +[
+  "string",
+  "null"
+]
  3. Addedv2.10.0
  4. Removedv2.9.0
  5. 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, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real value on top by disclosing the return shape (high/medium/low/package, null-or-absent when inactive) and warning that each URL is a bearer credential for live video that should not be repeated unprompted. That security caveat is behavior an annotation cannot express.

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?

Three tight sentences: what it does, what it returns, what to do instead, plus the credential caution. Everything is front-loaded and each sentence adds non-redundant information.

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?

An output schema exists, yet the description still explains the quality keys and null-when-inactive semantics, and it covers the sibling hand-off and the security constraint. Nothing an agent needs to call this correctly is missing.

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?

Schema description coverage is 100% and there is a single 'Camera ID' parameter, so the schema carries the burden; the description only implies the id refers to a camera without adding format or constraint detail. Baseline 3 is appropriate for a one-parameter tool fully documented in 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 and resource ('Get active RTSPS stream sessions for a camera') and scopes it precisely to the RTSP-stream concept. The sibling tools are all list/get entity tools, so a stream-session getter is clearly distinct, and the reference to protect_create_rtsp_stream further anchors it.

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 routes the agent to protect_create_rtsp_stream when it needs to start a session, which is genuine when-to-use guidance. It stops short of stating when not to call this tool (e.g. non-camera devices or no-session cases), so it is clear context rather than full routing.

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