Skip to main content
Glama

Read an exported review

get_review

Retrieves a saved code review as Markdown using a review ID or explicit review.json path, so agents can revisit and reuse prior review notes.

Instructions

Reads a saved review (by reviewId or an explicit review.json path) and returns it as Markdown.

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

Input Schema

NameRequiredDescriptionDefault
pathNoPath to review.json.
reviewIdNoIdentifier returned by start_review.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description must carry the behavioral burden. It does disclose the return format (Markdown) and implies a read-only operation, but says nothing about what happens when the review is missing, incomplete, or when neither optional parameter is supplied (required count is 0), nor whether the call blocks on a running review.

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?

A single front-loaded sentence with the verb first, the two input modes parenthetically, and the output format last. Nothing is redundant or padded.

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?

Because there is no output schema, the description correctly covers the return value as Markdown, which is the main gap it needed to fill. However, for a tool where both parameters are optional, the absence of any statement about default behavior or the zero-argument case leaves a meaningful hole.

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 one real semantic layer the schema lacks: the two parameters are alternatives ("by reviewId or an explicit review.json path"), which is not expressed by the schema's two independent optional properties. It still gives no precedence rule if both are provided.

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 a specific verb and resource ("Reads a saved review") and adds the two lookup modes plus the return format (Markdown). It implicitly separates itself from start_review/close_review by scoping to an already-saved review, but it never names a sibling or contrasts behavior explicitly, so it stops short of a 5.

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: an agent can infer this is the retrieval step after start_review, since reviewId is described in the schema as coming from start_review. There is no explicit statement of when to choose this over await_review or list_review_scope, and no guidance on when it would be wrong to call.

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