Skip to main content
Glama
Frigate MCP Server

Frigate MCP Server

by dedsxc

Get Cameras

get_cameras

List all cameras configured in Frigate with their names, status, and configuration details.

Instructions

Get the list of all cameras configured in Frigate.

Returns a list of cameras with their names, status, and configuration details.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses that the operation returns a list with names, status, and configuration details, which signals a read-only enumeration. It does not state whether cameras can be offline, whether results are paginated, or any authentication requirements, leaving some 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, front-loaded with the core action. The second sentence adds useful return-content detail without bloating, though it partially restates 'list of cameras' already implied by the first sentence.

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

Completeness4/5

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

This is a simple, zero-parameter read tool with an output schema, so the description does not need to document return structure in detail. It adequately covers what the tool does and what it returns, though it could mention whether the camera list is complete or filtered by configuration state.

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 tool takes zero parameters, so there is no parameter semantics to clarify; a baseline of 4 is appropriate. The description correctly implies no filtering inputs are needed, which aligns with the empty schema.

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 the list of all cameras configured in Frigate'), making the tool's purpose immediately clear and distinguishable from siblings like get_events or get_config. It does not explicitly name sibling tools or contrast with them, but the resource noun 'cameras' is unambiguous.

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 implied by 'all cameras configured in Frigate' — an agent would use this to enumerate cameras. However, there is no explicit when-to-use guidance, no mention of alternatives such as get_config (which might also reveal camera configuration), and no exclusions or prerequisites.

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