Skip to main content
Glama

queue_pr

Destructive

Adds a pull request to the Aviator merge queue so it merges automatically once required CI checks pass.

Instructions

Add a PR to the merge queue (Aviator merges it once CI passes).

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": {
      "number": "<number>"
    },
    "name": "queue_pr"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoGitHub org. Optional if repo is 'org/name'.
repoNoGitHub repo name or 'org/name'.
numberYesPull request number.
skip_lineNoJump to the front of the queue. Needs authorization; confirm with the user.
affected_targetsNo
skip_line_reasonNo
merge_commit_bodyNo
merge_commit_titleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare the operation as non-read-only, destructive, non-idempotent, and open-world. The description adds useful behavioral context by explaining that the PR is merged once CI passes, but it does not cover required authorization for queue-jumping, duplicate-enqueue behavior, failure handling, or other side effects of a destructive mutation.

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?

The definition is a single front-loaded sentence with no filler, and the parenthetical adds relevant outcome context. It is appropriately concise, though it is terse enough that some agents may need to infer the surrounding workflow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an eight-parameter destructive enqueue operation with no output schema, the description is notably incomplete. It explains the core queue action and CI-gated merge behavior but omits usage guidance, permissions, queue side effects, and most parameter semantics.

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?

The schema has eight parameters with only 50% description coverage, and the description provides no parameter-level meaning beyond identifying the PR. Undocumented parameters such as affected_targets, skip_line_reason, merge_commit_body, and merge_commit_title are left entirely to the schema, so the description does not compensate for the coverage gap.

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 uses a specific verb and resource: 'Add a PR to the merge queue,' and parenthetically explains the outcome that Aviator merges it once CI passes. It is clear what the tool does, but it does not distinguish this tool from siblings such as dequeue_pr or list_queued_prs.

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 explicit guidance on when to use this tool versus alternatives, nor any stated prerequisites or exclusions. Usage is only implied by the purpose statement, so an agent must infer the appropriate context.

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