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

ring-partner-mcp

by inslot2525-ctrl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Ring device details

ring_get_device
Read-onlyIdempotent

Retrieve status, capabilities, and configuration for a single Ring device using its device ID, including battery level, motion zones, encryption status, and sensor state.

Instructions

Status, capabilities and configuration for one device (battery, motion zones, encryption, sensor state).

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

Input Schema

NameRequiredDescriptionDefault
device_idYesDevice ID from ring_list_devices

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?

Beyond the behavioral annotations (readOnlyHint: true), the description provides crucial data context. It details exactly what specific configuration fields are included in the response (e.g., encryption, sensor state), which is highly valuable for the AI agent's expectation of the output.

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 a single, highly effective sentence that front-loads all necessary functional information (what is returned and for what purpose) without any filler.

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?

Given that it is a read-only tool with annotations covering safety, the description provides sufficient context by specifying the data points. It is complete for informing the agent about the utility and expected content of the returned data.

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%, making the baseline of 3 appropriate. The description mentions that `device_id` is a required string input, which is already fully captured by the schema, thus adding no meaningful semantic value beyond the structure.

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 clearly identifies the specific resource and action (retrieving status, capabilities, and configuration). By detailing the types of data returned (battery, motion zones, encryption), it is distinct from listing devices or viewing event history.

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?

While it doesn't explicitly say 'use this when,' the context of a single device retrieval implies it is the follow-up step after listing devices. It lacks explicit instruction on whether this is required in all cases or if related tools should be exhausted first.

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