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

ring-partner-mcp

by inslot2525-ctrl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Ring event history

ring_get_event_history
Read-onlyIdempotent

Retrieves past events for a Ring device, newest first, including doorbell presses, motion subtypes, and live views; supports limits and event-type filters.

Instructions

Past events for a device, newest first: doorbell presses (ding), motion (with subtypes), and live views (on_demand). Only events after the user granted consent to the app are available.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum events to return (default 20)
device_idYesDevice ID from ring_list_devices
event_typesNoFilter, e.g. ["ding"], ["motion.human", "motion.vehicle"], ["on_demand"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior and open-world access. The description adds useful behavioral context beyond annotations: results are ordered newest first, include specific event categories, and are limited to events after the user granted consent to the app. It does not mention pagination behavior or response shape, but the added consent constraint is a meaningful disclosure.

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?

The description is two sentences, front-loaded with the core purpose and scope, followed by an important consent caveat. Every sentence earns its place and there is no redundant or filler text.

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?

For a read-only event-history tool with full schema coverage and annotations covering safety traits, the description provides enough context to call it correctly: device targeting is implied, event types are illustrated, ordering is stated, and the consent limitation is disclosed. It does not describe pagination or response structure, but those are less critical given the schema and the absence of an output schema.

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 description coverage is 100%, so the schema already documents device_id, limit, and event_types with examples. The description reinforces event_types semantics by naming ding, motion subtypes, and on_demand, but does not add syntax or filtering details beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific resource and scope: 'Past events for a device, newest first,' and enumerates the relevant event categories (ding, motion, on_demand). It clearly distinguishes this from sibling tools like ring_list_devices and ring_get_snapshot by focusing on historical events rather than devices or current snapshots.

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?

The description implies when to use the tool by specifying that it returns past events for a device, but it does not explicitly say when to use it versus alternatives or state any exclusions. Sibling tools are clearly different, so the implied usage is adequate but not fully spelled out.

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