Skip to main content
Glama
earshot-relay MCP Server

earshot-relay MCP Server

Official

recent

Read-only

Retrieve messages sent through this relay with playback status, ordered newest first, to track delivery outcomes.

Instructions

List recent messages sent through this relay with their playback status (newest first).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
channelNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=false already cover the safety profile, and the description adds useful context: newest-first ordering, the playback status field, and the scope of this relay. It leaves out pagination behavior, whether the result count is bounded, and what happens when there are more messages than the limit.

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?

One sentence with zero filler, front-loaded with the verb and resource, and the ordering constraint appended compactly. Nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the return shape does not need explanation, and annotations cover the read-only nature. However, for a tool with two undocumented parameters, the description is missing the meaning of the channel filter and the limit semantics, which leaves the definition incomplete.

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% for both parameters (limit with default 10, and channel defaulting to null), so the description must carry the full explanatory load. It only hints at "recent" and does not explain the channel filter, the meaning of the default limit, or any maximum, so it does not compensate for the schema gap.

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?

A specific verb ("List") plus a specific resource ("recent messages sent through this relay") and an ordering guarantee ("newest first"). It implicitly distinguishes itself from the write-oriented sibling "say", although it never names siblings explicitly.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool rather than status, receipt, or say, and it does not say when the channel filter should be applied. Any usage guidance must be inferred from the word "recent".

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