Skip to main content
Glama
Sign In
Agent Guild

Agent Guild

by oddessentials
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Read a reply

read_reply
Read-only

Retrieve the full Markdown answer that ended a session's last turn using its session ID, so you can inspect the final response from supported coding agents.

Instructions

The whole text of the answer that ended a session's last turn, as Markdown. Only tools with reporting on (Claude Code, Codex CLI, Antigravity CLI, Grok Build, Docker Agent) have one.

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": {
      "session_id": "<session_id>"
    },
    "name": "read_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesThe session id from list_sessions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the availability constraint tied to reporting-capable tools and the Markdown return format. It stops short of saying what happens when reporting is off (empty result vs error), which would be the key remaining behavioral question.

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?

Two short sentences, front-loading the return content before the availability caveat. The phrase 'have one' is slightly elliptical, but nothing is wasted or padded.

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 single-parameter read tool with annotations and full schema coverage, this covers what is returned and when it is available. The main residual gap is failure behavior when the last turn has no reporting-backed reply, plus the missing contrast with read_replies.

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?

With one parameter at 100% schema description coverage, the schema already explains that session_id comes from list_sessions. The description adds no further meaning about the parameter, so the 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 description states precisely what is returned: 'the whole text of the answer that ended a session's last turn, as Markdown.' That is specific enough to distinguish it from a generic screen or transcript read. It does not, however, explicitly contrast itself with the sibling read_replies, leaving the singular/plural distinction to be inferred from the names.

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?

Usage is only implied — the agent must infer that this is the tool for retrieving the final assistant answer of a session. There is a useful precondition ('only tools with reporting on ... have one'), but no statement of when to prefer read_replies or read_screen instead.

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