Skip to main content
Glama
Frigate MCP Server

Frigate MCP Server

by dedsxc

Get Events

get_events

Retrieve recent Frigate detection events filtered by camera or object label, with a configurable result limit for focused security monitoring.

Instructions

Get recent detection events from Frigate.

Retrieves events based on optional filters for camera and detected object label.

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

Input Schema

NameRequiredDescriptionDefault
labelNoFilter by detected object label like 'person', 'car', 'dog' (optional)
limitNoMaximum number of events to return (default: 10, max: 100)
cameraNoFilter by specific camera name (optional)

Output Schema

NameRequiredDescriptionDefault
resultYes

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, the description carries the burden, but 'Get' adequately implies a non-mutating read, so there is no safety ambiguity. It does not disclose ordering of results, what 'recent' means as a time window, or any pagination behavior, leaving meaningful behavioral gaps.

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 with the core purpose front-loaded. The second sentence largely restates the filters already named in the first, making it mildly redundant rather than wasteful.

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?

An output schema exists, so return values needn't be explained, and the tool is a simple three-parameter read. However, for a listing tool, the absence of any statement about ordering, time window, or result volume ('recent') leaves the agent guessing about what it will get back.

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 label, limit, and camera are already fully documented in the schema. The description repeats camera and label filtering but adds no syntax, examples, or semantics beyond what the schema provides, and ignores limit entirely.

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?

States a specific verb and resource ("Get recent detection events from Frigate") and notes optional camera/label filters. It is clearly distinct from siblings like get_cameras, get_stats, or get_config, though it doesn't explicitly distinguish itself from get_event_details or get_recordings.

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 when-to-use guidance beyond the implicit 'list events' framing. Nothing tells the agent when to call get_events versus get_event_details or get_recordings, nor any exclusion or prerequisite.

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