Skip to main content
Glama
earshot-relay MCP Server

earshot-relay MCP Server

Official

say

Sends short text to a paired phone for spoken playback through Earshot; returns a message ID so callers can check whether it was played.

Instructions

Send a short message to be spoken aloud on the user's phone through Earshot. The text is stored in the user's bucket; if the Earshot app is listening it should speak it within seconds (Android text-to-speech by default, at the phone's media volume; held while the phone is on a call). A successful call means stored, not played. Keep it to one or two plain sentences. Returns the message id; call receipt with it to learn whether the phone played it. Not for the alarm channel: urgent alerts use the alarm tool, which exists only when the user enabled it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "say"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
voiceNo
speechNo
channelNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false; the description adds the delivery model (text stored in the user's bucket, spoken only if the Earshot app is listening, Android TTS at media volume, held during a call) and the critical caveat that a successful call means stored, not played. That caveat is exactly the kind of non-obvious behavior annotations cannot express.

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 tight paragraph that front-loads the core action, then layers delivery semantics, the success caveat, size guidance, and the alternative. Every sentence carries distinct information — nothing is restated from the annotations or schema.

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?

For a tool with an output schema, it covers return usage (message id, then receipt) and the asynchronous delivery model thoroughly, which is the main source of agent error here. The remaining gap is the unexplained voice/speech parameters, which the description leaves entirely to the schema.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description must carry the burden. It constrains 'text' (one or two plain sentences) and implicitly hints that 'channel' selects between speech and alarm delivery, but 'voice' and 'speech' are never mentioned and their meaning must be guessed from the names alone.

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?

States a specific verb and resource — send a short message to be spoken aloud on the user's phone via Earshot — and explicitly excludes the alarm channel in favor of the alarm tool. An agent can distinguish it from receipt, recent, and status without opening any schema.

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?

Gives positive guidance (one or two plain sentences), an explicit exclusion (not the alarm channel; urgent alerts use the alarm tool, which exists only when enabled), and a follow-up path (call receipt with the returned message id to learn whether it was played). Nothing about when to select this tool is left to inference.

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