Skip to main content
Glama

codex_review_request

Destructive

Fetch paginated code review request details for human review, following next_offset and verifying detail_sha256 to ensure complete content before acceptance.

Instructions

Human review, or read details with offset=0. Follow next_offset and verify detail_sha256. Acceptance requires complete content.

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
request_idNo
pending_request_idNoAlias of request_id

Output Schema

NameRequiredDescriptionDefault
okYes
result_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

C2.2/5.0
Behavior2/5

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

Annotations declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile comes from structured data rather than the text. The description adds the useful pagination protocol (follow next_offset, verify detail_sha256) and the 'acceptance requires complete content' rule, but never discloses the destructive/acceptance side effect that the annotations flag.

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

Conciseness3/5

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

Three short sentences, front-loaded with no filler, but the telegraphic style makes the first sentence ambiguous and leaves key protocol steps implicit. Brevity here costs clarity rather than adding it.

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?

An output schema exists, so return-value detail is not expected. However, for a destructive, open-world tool with four parameters and no required fields, the description leaves the ID-selection rule and the acceptance side effect unexplained, which is too thin.

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

Parameters2/5

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

Schema description coverage is only 25%, so the description must carry more weight. It explains offset=0 and the detail_sha256 verification, but says nothing about limit/page size, nothing about request_id vs the pending_request_id alias, and nothing about the anyOf requirement that one of the two IDs must be supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragments 'Human review' and 'read details with offset=0' gesture at two modes but never name the resource or state a clear verb-object pair. An agent cannot tell from this whether the tool submits something for review, retrieves a review request, or performs an acceptance action.

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?

'Human review, or read details with offset=0' implies two modes but gives no condition for choosing between them and no pointer to siblings such as codex_review or codex_requests. There is no when-not-to-use guidance.

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