Reflecto

List devices

list_devices

Read-onlyIdempotent

List the user's own paired Reflecto devices (their phone and desktop) and whether each is reachable. A phone counts as reachable when it has a live push registration, even if it is currently asleep or switched off — reachable does not mean the user is active on it right now. For recency use statusReportedAt (unix seconds of the last device status report); lastSeenAt is coarse (hourly) for phones. Read-only — returns device names and status metadata, never any message or notification content. Call this before send_notification when you need to pick a specific device — pass that device's deviceId, not its label, when you mean exactly one: labels can repeat across devices and a repeated label delivers to all of them.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`devices`	Yes

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description clarifies non-obvious behavior: a phone is reachable with a live push registration even while asleep or off, reachable does not mean actively in use, and statusReportedAt is the correct recency field because lastSeenAt is coarse for phones. It also confirms no message or notification content is ever returned.

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 front-loaded with the core purpose, then adds only high-value caveats about reachability, recency fields, and deviceId selection. Each sentence earns its place, and the dense detail is justified by the non-obvious behavior it explains.

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?

The tool is simple in parameters but has nuanced semantics, and the description covers the important nuances: device ownership, reachability definition, field-specific recency guidance, and correct use with send_notification. Since an output schema exists, return-value details do not need to be repeated in prose.

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?

The tool has zero parameters and 100% schema coverage, so there is no parameter-specific meaning for the description to add. The baseline for a no-parameter tool is met; the description appropriately focuses on output semantics instead.

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 verb and resource: 'List the user's own paired Reflecto devices ... and whether each is reachable.' It also disambiguates why this tool exists relative to send_notification by explaining that it is the lookup step before picking a device.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool: 'Call this before send_notification when you need to pick a specific device.' It also gives a concrete when-not: use deviceId rather than label when targeting exactly one device, because repeated labels deliver to all devices.

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

All Reflecto tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Every tool has a clearly distinct purpose: reminders (remind_me/cancel_reminder), approvals (request_approval/check_reply), notifications (send_notification), files (send_file), device info (list_devices), shared items (get_shared_items), and phone locating (find_my_phone). No two tools overlap in action or resource.

Naming Consistency5/5

All nine tools follow a consistent snake_case verb_noun pattern, e.g., cancel_reminder, send_notification, list_devices. There are no deviations or mixed conventions.

Tool Count5/5

Nine tools is well-scoped for a phone-communication server. Each tool addresses a distinct functional need without redundancy or bloat, making the set feel purposeful and easy to navigate.

Completeness5/5

The surface covers the essential lifecycle for its domain: scheduling and canceling reminders, requesting and polling approvals, sending notifications and files, reading user-shared items, listing devices, and locating the phone. No obvious gaps or dead ends exist.

Resources

Need Help?