Skip to main content
Glama
Sign In
ring-recap-mcp

ring-recap-mcp

by headlessfounder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Sync one day of Ring clips

sync_day

Pulls, transcribes, describes, and recaps Ring camera clips for a date (default yesterday), processing only unfinished footage and returning a run summary or progress.

Instructions

Pulls, transcribes, describes and recaps every clip at the configured location for a date (default yesterday). Idempotent: only clips not already done are processed. Returns the run summary, or progress if it is still running (call again to check).

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD, local time. Defaults to yesterday.
stageNoStop after this stage (download, audio, frames, describe, faces) or run everything (all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false; the description adds the materially important traits: idempotent filtering of already-processed clips and an asynchronous run that may return progress instead of a final summary, with the instruction to poll again. It does not say where output is stored or how long a run takes, but the async/polling behavior is the key disclosure a caller needs.

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

Conciseness5/5

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

Three short sentences, each carrying distinct information: what it does, the idempotency guarantee, and the return/polling behavior. The scope and default are front-loaded, and nothing is redundant.

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

Completeness5/5

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

With no output schema, the description still explains the return value (run summary, or progress when still running), which is the main gap such tools leave. Combined with a fully documented schema and disclosed idempotency, an agent has everything needed to call it and handle the response.

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 coverage is 100%, so both the date format/default and the stage enum values are already documented in structured fields. The description only restates the yesterday default and adds 'configured location', which is context rather than parameter meaning; the stage parameter's stop-after semantics are left entirely to the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific chain of verbs (pulls, transcribes, describes, recaps) applied to a concrete resource (every clip at the configured location) scoped to a date. An agent can immediately distinguish this pipeline tool from the siblings list_cameras and health, which are trivially different in scope.

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

Usage Guidelines4/5

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

It gives the practical calling context: the date defaults to yesterday, the operation is idempotent so re-running is safe, and if progress is returned you should call again to check. There is no explicit 'do not use when' or named alternative, but the siblings are unrelated capabilities rather than substitutes, so the guidance is close to complete.

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

Deploy Server

Other Tools