Skip to main content
Glama
Frigate MCP Server

Frigate MCP Server

by dedsxc

Get Stats

get_stats

Retrieves Frigate NVR system statistics and performance metrics—CPU usage, memory, detector performance, camera FPS, and detection metrics—to monitor and troubleshoot system health.

Instructions

Get Frigate system statistics and performance metrics.

Returns information about CPU usage, memory, detector performance, camera FPS, and detection metrics.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

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 full burden; it implies a passive read by listing returned metrics but never states that it is read-only, side-effect free, or whether it requires auth or polling. It does enumerate the data domains (CPU, memory, detector, camera FPS, detection metrics), which is useful behavioral context beyond nothing.

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 purpose and followed by the returned data categories. Minor redundancy between 'statistics and performance metrics' and the enumeration that follows, but no wasted padding.

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?

An output schema exists and there are no parameters, so the description only needs to set expectations for scope, which the metric list does adequately. It could be stronger by saying what the tool does not cover (e.g., configuration, which belongs to get_config).

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?

Zero parameters, so there is no parameter semantics to add; the baseline of 4 applies. The description correctly avoids inventing parameters.

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 Frigate system statistics and performance metrics') and names the categories of data returned. It is distinguishable from most siblings (get_cameras, get_events, get_recordings), though the boundary with get_config is not made explicit.

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 listed data categories; there is no statement of when to prefer this over get_config or system-level alternatives, 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.