Skip to main content
Glama
earshot-relay MCP Server

earshot-relay MCP Server

Official

status

Read-only

Returns available sendable channels, speech modes, and the last beacon from each paired phone so you can check relay readiness before sending spoken text or audio.

Instructions

Relay status: sendable channels, speech modes, and the last beacon from each phone.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered, and the presence of an output schema removes the need to document return shape. The description still contributes by declaring the scope of the payload (channels, speech modes, per-phone beacon), but adds nothing about freshness, cost, or whether the beacon data is live.

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 front-loaded sentence that lists the three payload components in order of usefulness. No filler and nothing repeated from the schema or annotations.

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 zero-parameter read tool with an output schema and safety annotations, the description covers what remains. The only real omission is any hint about when in a workflow to call it, which is minor given the output schema fully documents the response.

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?

Zero parameters, so the baseline is 4; the description correctly implies no input is required to obtain status. Nothing further is needed from the description here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the resource (relay status) and enumerates exactly what it reports: sendable channels, speech modes, and the last beacon per phone. That is concrete enough to distinguish it from siblings like 'receipt' and 'recent', though the phrasing is noun-only with no verb and no explicit contrast to those siblings.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use statement, and no sibling is named. Usage is only implied — 'sendable channels' and 'last beacon from each phone' suggest a preflight check before using 'say', but the agent must infer that.

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