Skip to main content
Glama
EminUZUN

hoptell

by EminUZUN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

read_inbox

Retrieve messages received from peers and acknowledge handled batches, enabling agents to process incoming work delivered through the hoptell relay.

Instructions

Return messages received from peers. Listener command (listener delivery only): (shown once connected: call list_peers, then list tools again). Review a snapshot's supplied content; its file label is not a local path. Reply with review_request_id, based_on set to its sha256, and reply_to when available. Before using a local checkout, run '/usr/bin/node' '/app/bin/hoptell.js' snapshot --check <received-sha256> <local-file> and report match, mismatch or unable to check. On mismatch or failure, review the supplied content; local tests do not validate it. A review set (hoptell_review_set) lists files by file_id. Use its content only if hoptell's Review set check after the matching end marker says every file's content matches its sha256. The sender's user reviews and applies proposals; do not claim one was applied.

Input Schema

NameRequiredDescriptionDefault
ackNoOptional. The receipt returned with a message batch you have finished handling.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / ack
      Added value: +{
+  "description": "Optional. The receipt returned with a message batch you have finished handling.",
+  "type": "string"
+}
  2. First observedv0.1.1

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must disclose whether this is a safe read and whether reading consumes or acknowledges messages; it does neither. It includes lab instructions for snapshot verification and review sets, which are post-reception procedures rather than the tool's own behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the bulk of the description is a rambling mini-manual about snapshot checks, hoptell CLI invocations, and review sets. Much of it does not help an agent decide to call read_inbox or understand its result.

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

Completeness2/5

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

For a message-reading tool with no output schema and no annotations, the description should explain the shape of returned messages and how ack is used. Instead it omits return-value information and fills space with external verification steps.

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

Parameters3/5

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

Schema coverage for the single ack parameter is 100%, so the schema already defines it. The description never mentions ack or adds format/meaning beyond the schema; baseline 3 applies.

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?

The opening sentence gives a clear verb and resource: return messages received from peers. It does not distinguish read_inbox from wait_for_message or ack_messages, and the subsequent procedural text about snapshots and review sets is not about this tool's purpose, which slightly muddies the signal.

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 a cryptic listener-mode note but never states when to call read_inbox instead of wait_for_message or ack_messages. The reply/check instructions are conditional workflow after receiving a message, not guidance on tool selection.

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