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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedSep 4, 2026

addedOutput schema / properties / devices / items / properties / clientBrowser

Added value: +{
+  "description": "Browser brand for a PC surface, e.g. Chrome or Edge. Absent for phones.",
+  "type": "string"
+}

addedOutput schema / properties / devices / items / properties / clientOs

Added value: +{
+  "description": "OS brand for a PC surface, e.g. macOS or Windows. Absent for phones.",
+  "type": "string"
+}

Changed2 schema fields changedAug 24, 2026

addedOutput schema / properties / devices / items / properties / deviceId

Added value: +{
+  "description": "Stable opaque id. Pass this as send_notification's `device` to reach exactly one device — labels are NOT unique, and a shared label delivers to every device that has it.",
+  "type": "string"
+}

changedOutput schema / properties / devices / items / required

Previous value: -[
-  "label",
-  "type",
-  "reachable",
-  "lastSeenAt"
-]New value: +[
+  "deviceId",
+  "label",
+  "type",
+  "reachable",
+  "lastSeenAt"
+]

First observedAug 24, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark this as read-only and idempotent, but the description adds valuable nuance beyond that: a phone counts as reachable with a live push registration even when asleep or off, statusReportedAt is the reliable recency field, and lastSeenAt is coarse for phones. It also clarifies it never returns message or notification content.

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?

Every sentence earns its place: scope, reachability, recency guidance, safety, and usage routing are each a separate needed piece. The description is longer than minimal but wastes no words and front-loads the core purpose.

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?

For a zero-parameter read-only tool with an output schema, the description covers all important operational caveats: reachability semantics, recency field choice, and deviceId/label handling. An agent has enough to invoke it correctly and act on the 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?

There are no parameters, so the schema leaves nothing to explain. The description still adds relevant semantics around output identifiers—deviceId versus label—which indirectly helps correct downstream use, keeping this above the baseline.

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 opens with a specific verb and resource: 'List the user's own paired Reflecto devices... and whether each is reachable.' It clearly differentiates this tool from siblings like send_notification by scoping it to device enumeration and status, not sending or locating.

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 states when to use this tool: 'Call this before send_notification when you need to pick a specific device.' It also provides a concrete usage warning—pass the deviceId, not the label, because repeated labels deliver to all—which prevents a common mistake.

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?