Skip to main content
Glama
WatermelonBros

Reado

by WatermelonBros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

review_context

Read-onlyIdempotent

Retrieve a file's review context before reviewing it: session objective, ranking rationale, state, summary, and existing proposals. Use session_show for the full session.

Instructions

Read one file's context in a guided review before reviewing it, as JSON: the session objective, the file's route entry (why it was ranked, related files), its state, its running summary and the proposals already on it. For the whole session use session_show.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesProject-relative path, e.g. `src/lib/api.ts`.
sessionIdNoThe session id from the READO GUIDED REVIEW prompt. Omit it to use the newest session still open.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.32.1
    • addedInput schema / properties / file / description
      Added value: +"Project-relative path, e.g. `src/lib/api.ts`."
    • addedInput schema / properties / sessionId / description
      Added value: +"The session id from the READO GUIDED REVIEW prompt. Omit it to use the newest session still open."
  2. First observedv1.32.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. With no output schema, the description usefully discloses the read is and what it contains, which is real added value beyond 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?

Front-loaded with verb and scope, then the field inventory, and the sibling redirect is held to the end. The field list is a touch long but each item earns its place since no output schema exists.

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 two-parameter read tool with no output schema, the description carries the return-shape burden well by enumerating the JSON payload. Nothing an agent needs to invoke it correctly appears to be missing.

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 description coverage is 100%, so both 'file' and 'sessionId' (including the newest-session default) are already documented in the schema. The description adds no syntax or format detail beyond that, so baseline 3 applies.

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 ('Read') and resource ('one file's context'), enumerates the returned fields (objective, route entry, state, summary, proposals), and explicitly distinguishes itself from the session_show sibling. An agent can identify the scope as single-file versus session-wide without opening the 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?

Gives timing ('before reviewing it') and names the alternative for whole-session needs ('For the whole session use session_show'), which routes the agent correctly. It offers clear context but no explicit when-not-to-use beyond the sibling redirect.

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