Skip to main content
Glama
Frigate MCP Server

Frigate MCP Server

by dedsxc

Get Recordings

get_recordings

Retrieve a camera's recording summary and storage details for a specific date, or today by default, to check available recordings.

Instructions

Get recording information for a specific camera.

Retrieves the recording summary including available recordings and storage information for a camera on a specific date.

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": "<camera>"
    },
    "name": "get_recordings"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format (optional, defaults to today)
cameraYesName of the camera

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden; it does convey that this is a read of recording and storage information, which establishes a non-mutating profile. It says nothing about behavior when a camera has no recordings on the date, camera-name resolution failures, permissions, or volume of results — meaningful gaps for a completely unannotated tool.

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?

Two short sentences, front-loaded with the core action, and zero filler. There is mild redundancy: 'Get recording information' is immediately rephrased as 'Retrieves the recording summary,' which is a partial restatement rather than new information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required param, flat schema, output schema present, so return shape needn't be described) and the description covers purpose and returned content. However, with no annotations it should do more to cover empty-result and failure behavior, and it provides no routing against closely related read tools.

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%, so both 'camera' and 'date' (including the YYYY-MM-DD format and today-default) are already documented in the schema. The description only restates that the lookup is scoped to a camera and a date, adding no new semantics such as name matching rules or timezone handling.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Get recording information for a specific camera') and expands the scope to recording summary, available recordings, and storage information. The resource is clearly distinct from siblings like get_cameras, get_events, and get_snapshot, though it never explicitly contrasts itself with them.

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?

There is no guidance on when to use this versus get_snapshot, get_events, or get_event_details, and no prerequisites or exclusions are stated. The camera+date framing implies a retrieval context but leaves the agent to infer selection criteria entirely.

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