Skip to main content
Glama
earshot-relay MCP Server

earshot-relay MCP Server

Official

receipt

Read-only

Returns a sent message's device-playback status, showing whether it finished, was skipped, failed, or was missed, and can wait up to 60 seconds for a final result.

Instructions

Did the phone play it? Returns the device-playback receipt of a message (id from say or alarm, or 'latest'): stored, detected, started, finished, skipped (the user skipped it), failed, missed (not played: it went stale, the bucket changed or audio was unavailable) or unconfirmed (no device report yet). wait_seconds (0-60) waits for a final status; final says whether waiting longer could still change it. A finished receipt means the phone finished playing it, not that a person heard it.

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

Input Schema

NameRequiredDescriptionDefault
idNolatest
wait_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say read-only and not open-world; the description adds substantial behavior beyond that by enumerating every possible receipt state with plain-language meanings (skipped, missed with its three causes, unconfirmed) and explaining the final flag. The closing caveat that a finished receipt does not mean a person heard it is exactly the kind of semantic nuance annotations cannot convey.

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?

Front-loaded with the core question and answer, then statuses, then waiting behavior, then a closing caveat. The parenthetical enumerations are dense but each adds decision-relevant meaning, and there is no filler or repetition.

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 two-parameter read tool with an output schema, everything an agent needs is present: what is returned, what each state means, how to wait, and how to interpret a 'finished' result. Nothing essential is deferred to guesswork, and return-value structure is appropriately left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full load, and it does: it defines what id accepts (say/alarm message id or 'latest') and the semantics and range of wait_seconds (0-60, waits for a final status). An agent can set both parameters correctly without further documentation.

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?

Opens with a concrete question ('Did the phone play it?') and immediately names the resource: the device-playback receipt of a message. It scopes the id source ('from say or alarm, or latest'), which tells an agent exactly what this returns and how it differs from siblings like status or recent.

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

Usage Guidelines4/5

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

Clear usage context: the id must come from say or alarm, or be 'latest', and wait_seconds is framed as the way to wait for a final status rather than snapshotting. It does not explicitly state when to prefer a sibling such as status or recent, so it stops short of full when/when-not guidance.

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