Skip to main content
Glama

review_queue

Lists pull requests awaiting review across all projects, ordered by milestone blockers first and then longest wait, with status for clean builder checks and outdated prior verdicts.

Instructions

The pull requests waiting for review across every project, in the order to take them: those blocking their milestone first, then the longest waiting. Each says whether the builder's Codex layer is clean and whether an earlier verdict is for an older commit.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the ordering rule (milestone-blocking first, then longest waiting) and the per-item signals returned (Codex-layer cleanliness, stale-verdict-against-older-commit). What's missing is pagination, size limits, or whether the list is filtered by the calling user.

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?

Three short sentences, front-loaded with the resource and its ordering rationale; every clause carries information. Some terminology ('builder's Codex layer') is unexplained jargon that a fresh agent may not decode, which keeps it below the top mark.

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?

An output schema exists, so return values need not be explained, and the description still covers ordering semantics and the key per-item flags. For a zero-argument read tool this is nearly sufficient; only volume and pagination behavior are unaddressed.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies the tool is parameterless by framing the result as a fixed, server-ordered queue.

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?

States a specific resource and scope: pull requests waiting for review across every project, plus the sort order used to present them. An agent immediately knows this is a read of the review backlog, though the description never names how it differs from near-siblings such as record_review or review_brief.

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 phrase 'in the order to take them' implies this is the entry point for working a review queue, which is useful contextual guidance. However, there is no explicit statement of when to prefer it over record_review or review_brief, and no exclusions or prerequisites are given.

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