Skip to main content
Glama

list_queued_prs

Read-onlyIdempotent

Fetches pull requests in the merge queue, ordered by queue position, returning number, title, author, and status so users can inspect what is waiting to merge.

Instructions

PRs currently in the merge queue, in queue order (number, title, author, status).

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_queued_prs"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoGitHub org. Optional if repo is 'org/name'.
repoNoGitHub repo name or 'org/name'.
limitNo
base_branchNoOnly PRs targeting this branch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context by promising queue order and the returned field set, but says nothing about permissions, rate limits, or pagination behavior for the limit parameter.

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?

A single compact sentence, front-loaded with the resource and ordering guarantee, with the returned fields efficiently parenthesized. No wasted words, though the parenthetical is terse enough to be slightly cryptic.

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, naming the returned fields is a valuable compensation. However, for a four-parameter list tool with no required params, the description omits default behavior, how limit interacts with the queue, and when this tool is the right choice.

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 75%, with org, repo and base_branch documented in the schema, so the baseline is 3. The description adds nothing about any parameter, notably leaving limit and base_branch semantics to the schema alone.

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 specific resource (PRs in the merge queue) with an explicit ordering guarantee and the returned fields, so the agent knows exactly what it gets. It stops short of differentiating from siblings like queue_pr or dequeue_pr.

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?

There is no when-to-use guidance, no mention of prerequisites, and no reference to related siblings such as queue_pr, dequeue_pr, or get_queue_stats that an agent might pick instead. Usage has to be inferred entirely from the description.

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