Skip to main content
Glama

Wait for the submitted review

await_review

Blocks until the review page submits a review, then returns all inline comments and paths to review.json and review.md.

Instructions

Blocks until the review page submits a review, then returns every inline comment plus paths to review.json and review.md.

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": {
      "reviewId": "<reviewId>"
    },
    "name": "await_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
reviewIdYesIdentifier returned by start_review.
timeoutSecondsNoSeconds to wait. Default 120.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the call blocks and what the return contains, but it says nothing about what happens when timeoutSeconds expires, whether the call is safe to repeat, or whether the returned comments are complete or current.

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?

It is a single sentence that front-loads the blocking behavior and then states the return payload. Every clause adds information, and there is no restatement of the name or title.

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?

With no output schema, the description must explain the return value, and it does so in part: inline comments plus paths to review.json and review.md. However, it omits timeout and expiry behavior, which matters for a tool that can block for up to an hour, so it is not fully complete for the tool's complexity.

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 coverage is 100%, so the schema already documents reviewId and timeoutSeconds, including the default and maximum. The description adds no parameter-level detail beyond that, which is appropriate at the baseline.

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 names a specific verb and resource: it blocks until the review page submits a review, then returns the results. That distinguishes it implicitly from get_review, which is non-blocking, even though the sibling is not named explicitly.

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?

The blocking nature implies when to use it: when an agent must wait for a human to submit a review. However, the description gives no explicit when-to-use or when-not-to-use guidance and does not point to get_review or close_review when waiting is not desired.

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