Skip to main content
Glama

Prior Ledger

review_queue

Read-only

Reviewer tokens only. Proposals waiting for a decision, with any reviews already recorded. Read REVIEWING.md in the repository before reviewing.

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
statusNopending

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description's main additions are the token-scope restriction and the REVIEWING.md prerequisite. Beyond that it says nothing about ordering, pagination, or how many proposals come back, so it adds only partial behavioral context.

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 with the audience and scope front-loaded, then the doc pointer. Nothing is padded, though the REVIEWING.md reference is a dangling pointer whose payoff is unclear from the definition alone.

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?

For a simple single-parameter read tool with no output schema, it covers who may call it and what it returns at a high level. It is incomplete on the one thing that is not machine-documented: the status parameter's vocabulary and effect.

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?

There is exactly one parameter (status, default "pending") with 0% schema description coverage, so the description carries the full burden of explaining it. The phrase "waiting for a decision" hints at the pending default but never names the parameter, its accepted values, or what other statuses would return.

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 the resource and filter concretely: "Proposals waiting for a decision, with any reviews already recorded." An agent can tell this is a read of the pending-review backlog rather than a single proposal (proposal_status) or a review action (review_proposal). It names the audience (reviewers) but not an explicit verb like "list."

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?

"Reviewer tokens only" establishes an access prerequisite and "Read REVIEWING.md before reviewing" adds a procedural prerequisite, which is useful context. However, it never says when to call this versus proposal_status or the individual review/accept/reject tools, so the choice among siblings is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.