Skip to main content
Glama
Frigate MCP Server

Frigate MCP Server

by dedsxc

Get Config

get_config

Retrieve the complete Frigate configuration—cameras, detectors, motion settings, and system settings—to inspect or troubleshoot your NVR setup.

Instructions

Get the complete Frigate configuration.

Retrieves the full Frigate configuration including all cameras, detectors, motion settings, and system configuration.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'Get' implies a read-only operation and 'complete' signals the whole config is returned, but it says nothing about permissions/auth required, whether secrets or credentials appear in the payload, or the size/cost of the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The second sentence largely restates the first ('full Frigate configuration' after 'complete Frigate configuration'). The enumeration of cameras, detectors and motion settings does add scope information, but the lead sentence already front-loads everything, making the rest partly redundant.

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 return values need not be described. The description adequately conveys what the call returns; only auth/permission expectations and payload caveats are missing, which is a modest gap for a read-only fetch.

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 nothing to disambiguate; the baseline for a parameterless tool applies. The description correctly avoids inventing parameters and simply states the resource returned.

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 the complete Frigate configuration') and enumerates scope (cameras, detectors, motion settings, system configuration). The word 'complete' implicitly distinguishes it from narrower siblings like get_cameras or get_stats, though it never names them explicitly.

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 by the word 'complete' — an agent can infer this is the broad fetch versus the narrower per-resource siblings, but there is no explicit statement of when to prefer this over get_cameras or get_stats, and no prerequisites or exclusions noted.

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