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

ring-partner-mcp

by inslot2525-ctrl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a Ring camera snapshot

ring_get_snapshot
Read-onlyIdempotent

Retrieves a recent JPEG snapshot from a Ring camera within a specified past time window and rejects end-to-end encrypted cameras.

Instructions

The most recent recorded image from a camera within the last N minutes, returned as a JPEG. Refuses cameras with end-to-end encryption.

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": {
      "device_id": "<device_id>"
    },
    "name": "ring_get_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_idYesCamera device ID from ring_list_devices
component_idNoCamera module on multi-camera devices such as Ring Elite
within_minutesNoHow far back to look (default 15, max 1440)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real context beyond them: the payload is a JPEG, it is a recorded frame rather than a live stream, the recency window is bounded, and there is a hard failure mode for E2E-encrypted cameras. Not stating what the refusal looks like (error vs empty) is the remaining gap.

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?

Two sentences, zero waste, with the return type and recency constraint front-loaded before the refusal caveat. Nothing could be removed without losing information.

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?

With only 3 fully documented parameters, no output schema, and annotations covering safety, the description supplies what is missing: the return medium (JPEG) and the encryption refusal. A note on auth requirements or pagination/size behavior would round it out but is not essential here.

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% and every parameter is documented in the input schema, so the baseline of 3 applies. The description echoes the within_minutes semantics ('within the last N minutes') but adds no format, default, or constraint detail the schema does not already carry.

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 ('get') and resource ('snapshot') and pins down the semantics: the most recent recorded image within N minutes, returned as JPEG. It implicitly separates itself from ring_get_event_history and ring_list_devices, though it never names a sibling explicitly.

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?

'Refuses cameras with end-to-end encryption' gives a concrete exclusion condition, and 'most recent recorded image' tells the agent this is not a live view or a history query. No alternative tool is named for the refused case, so it stops short of full when-to-use routing.

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