Skip to main content
Glama

Read the review queue

list_review_queue
Read-only

Preview up to three grounded cards with evidence and review status without recording an exposure; use the presentation flow or CLI to record the daily allowance when showing recommendations.

Instructions

Preview up to three grounded cards without recording an exposure.

    Cards include their evidence and review status. Use present_review_queue or
    CLI review present when showing recommendations to record the daily allowance.
    

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

Input Schema

NameRequiredDescriptionDefault
limitNo
topic_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds the crucial side-effect distinction: this call does not record an exposure/allowance, unlike the alternative. It also notes cards include evidence and review status, useful return-context beyond annotations.

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?

Two short sentences, front-loaded with the no-side-effect constraint and followed by the alternative. Minor wasted indentation/formatting noise but no filler prose.

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?

Output schema and annotations cover return shape and safety, and the description adds the exposure-recording distinction. However, with an entirely undocumented topic_id filter and no explanation of limit bounds, an agent cannot confidently use the filtering capability.

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 coverage is 0%, so the description must carry parameter meaning. It partially clarifies limit via 'up to three' (matching the default of 3), but never names the limit parameter or explains its bounds, and topic_id is not mentioned at all — a real gap for a filtering parameter.

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 action (preview grounded cards) and a key scope constraint (no exposure recorded). 'Grounded cards' is specialized vocabulary but is repeated in the sibling tool name context, so an agent can tell this apart from the recording variant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to present_review_queue / CLI review present when actually showing recommendations and needing to record the daily allowance. Clear when-to-use-this-instead-of-that guidance, though it doesn't say when not to preview at all.

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