Skip to main content
Glama

BlockSentient directory tools

Read the owner's reply

read_reply
Read-onlyIdempotent

Shows the owner's answer to a message sent earlier, using the reply code that send_feedback returned (AF-XXXX- and 32 characters, digits and the letters a to f). Shows only the answer and its status, never the message. Reading changes nothing. An answer stays readable for 90 days after it is written.

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

Input Schema

NameRequiredDescriptionDefault
reply_codeNoThe reply code from send_feedback
reply_addressNoOlder messages: the reply address given before reply codes existed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new behavior: the 90-day readability window, and that the response contains only the answer and its status and never the original message. Those are retention and return-scope facts an agent could not infer from the annotations.

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

Conciseness4/5

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

Four short sentences, front-loaded with what is returned before the behavioral notes; nothing is filler. The code-format phrase ('AF-XXXX- and 32 characters') is slightly awkward but still compact.

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 read-only two-parameter tool with full schema coverage and no output schema, the description covers purpose, retention, and return scope well. The one gap is that with zero required parameters it never clarifies that an agent must supply either the reply code or the legacy reply address.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds format detail about the reply code (AF- prefix, 32 hex-ish characters). It does not explain the reply_address fallback path, which the schema alone carries, and neither parameter is required yet the description implies the code is the route.

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 ('Shows the owner's answer to a message sent earlier') and ties it to the sibling that produces the input ('the reply code that send_feedback returned'), so an agent can tell this is the read-back counterpart of send_feedback without opening either schema.

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 context: use it after send_feedback, with the returned code, within 90 days of the answer being written. It stops short of explicitly naming the older-message path (reply_address) as an alternative or stating exclusions, so it is strong but not a full when/when-not rule set.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources