Reflecto

This connector has been deprecated

This connector has been replaced by 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?

Annotations already declare readOnlyHint=true, but the description adds meaningful context beyond that: it explains the semantics of 'reachable' (live push registration, regardless of active use), clarifies that lastSeenAt is coarse for phones, and reassures that no message or notification content is ever returned. No contradiction with annotations.

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 dense but every sentence earns its place: core purpose, clarifications of ambiguous terms, field-usage tips, and downstream guidance. It is front-loaded with the primary action and resource, then builds on that efficiently without redundancy.

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?

With no output schema provided, the description carries the burden of explaining return values and it succeeds: it names device names, status metadata, statusReportedAt, lastSeenAt, deviceId, and labels. It also explains the meaning of reachability and warns about label duplication. An agent has everything needed to call this tool and correctly use its results.

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 input schema has zero parameters, so there is nothing for the description to explain about this tool's inputs. The description does add useful semantics about output fields (deviceId vs label, statusReportedAt vs lastSeenAt) that will be consumed by other tools, which is a bonus. Baseline 4 for zero params is appropriate.

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 states a specific verb ('List'), a concrete resource ('the user's own paired Reflecto devices'), and the key information returned (whether each is reachable). It explicitly contrasts with send_notification, so an agent can clearly distinguish this listing tool from the send tool without ambiguity.

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?

It explicitly says 'Call this before send_notification when you need to pick a specific device' and warns against passing labels when targeting exactly one device, since labels can repeat and deliver to all. It also provides field-selection guidance (statusReportedAt vs lastSeenAt) for recency, leaving no doubt about when and how to use the tool.

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.5/5.0

Disambiguation5/5

Each tool targets a distinct action: scheduling vs cancelling reminders, pushing vs ringing a phone, sending vs receiving files/shared items, and requesting vs polling approvals. The only close pair, send_notification and remind_me, is clearly separated by immediacy vs future scheduling, and the descriptions reinforce the boundary.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: cancel_reminder, check_reply, get_shared_items, list_devices, request_approval, send_file, send_notification. Minor possessive forms like find_my_phone and remind_me still fit the imperative verb-first style without creating confusion.

Tool Count5/5

Nine tools is well within the ideal range and each one earns its place in a personal-device integration server. The surface covers notifications, reminders, approvals, shared items, file delivery, device discovery, and phone location without redundant or filler tools.

Completeness4/5

Core workflows are covered: reminders can be scheduled and cancelled, approvals can be requested and polled, notifications can be sent, and shared items can be read incrementally. Minor gaps exist, such as no way to cancel a pending approval and no update mechanism for reminders, but these are workable and the server is explicitly stateless about some of them.

Resources

Need Help?