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

ring-partner-mcp

by inslot2525-ctrl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Ring devices

ring_list_devices
Read-onlyIdempotent

Lists Ring devices shared with the app, showing each device's kind, online status, and whether video is end-to-end encrypted.

Instructions

List the Ring devices shared with this app, with kind (camera, contact_sensor, ...), online state and whether video is end-to-end encrypted.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuine value beyond them by naming the payload an agent will get back (kind, online state, end-to-end encryption status), which shapes downstream decisions.

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?

A single sentence that front-loads the action and scope, then lists the returned attributes. No filler, nothing to trim.

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 no output schema, the description usefully enumerates the key returned fields and the sharing scope, which is enough to call it correctly. It does not mention ordering, limits, or whether an empty result is possible, but those are minor for a no-arg list call.

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?

There are zero parameters, so the baseline is 4 and nothing in the description needs to compensate. No parameter-level guidance is required or given.

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+resource ('List the Ring devices') and adds scope ('shared with this app'), which distinguishes it from ring_get_device by name alone. It stops short of explicitly contrasting with the siblings, so it is clear but not fully differentiated.

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?

Enumeration is the implied first step before ring_get_device / ring_get_snapshot, but the description never says when to use this versus those alternatives or whether it is the entry point for discovery. Usage is inferable from the verb 'List' rather than stated.

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