Skip to main content
Glama
Frigate MCP Server

Frigate MCP Server

by dedsxc

Get Event Details

get_event_details

Retrieve complete details for a specific Frigate detection event, including zones, thumbnails, clips, and timeline data to review what happened.

Instructions

Get detailed information about a specific detection event.

Retrieves comprehensive details including zones, thumbnails, clips, and timeline information for a single event.

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": {
      "event_id": "<event_id>"
    },
    "name": "get_event_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesThe unique ID of the event to retrieve

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the payload contents (zones, thumbnails, clips, timeline), which is genuinely useful, but it never states that the operation is read-only, whether media URLs expire, whether large clips are truncated, or any permission requirements — significant gaps for an 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 followed by the payload summary. Minor redundancy between 'detailed information' and 'comprehensive details', but nothing extraneous.

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 and has an output schema, so return values needn't be explained, and the description covers purpose plus a rough sense of the payload. What is missing is the usage relationship to get_events and any behavioral caveats to compensate for the absence of annotations.

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?

Only one parameter and schema coverage is 100%, with 'The unique ID of the event to retrieve' already documenting it fully. The description adds no format hints (e.g., where an event_id comes from or what an invalid ID yields), so the baseline 3 applies.

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?

Names a specific verb and resource ('Get detailed information about a specific detection event') and scopes it to a single event, which implicitly separates it from the list-style sibling get_events. It stops short of explicitly naming that sibling, so the differentiation must be inferred from the word 'single'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the required event_id signals that this is a follow-up drill-down after obtaining an ID elsewhere. There is no explicit statement of when to prefer this over get_events or what to do if the ID is unknown, and no exclusions or prerequisites are given.

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