Skip to main content
Glama

dequeue_pr

Destructive

Remove a pull request from the merge queue and clear its skip-line options to prevent it from being merged.

Instructions

Remove a PR from the merge queue (also clears its skip-line options).

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

Input Schema

NameRequiredDescriptionDefault
orgNoGitHub org. Optional if repo is 'org/name'.
repoNoGitHub repo name or 'org/name'.
numberYesPull request number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuine value beyond that by disclosing a secondary side effect not visible in the schema: skip-line options on the PR are also cleared. It stops short of explaining failure behavior for a non-queued PR.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the primary action first and the side effect in a parenthetical. Nothing is wasted and there is no preamble.

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?

For a three-parameter mutation whose annotations already flag destructiveness and non-idempotency, the definition covers the essential behavior. The remaining gap is the failure mode when the PR is not in the queue, plus any hint about what the call returns, but neither blocks correct invocation.

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 100%, with org, repo and number all documented in the schema, including the 'org/name' shorthand and the positivity constraint on number. The description adds no parameter-level detail, so the baseline 3 applies.

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 verb and resource ('Remove a PR from the merge queue'), which is unambiguous and clearly the inverse of the sibling queue_pr. The parenthetical adds a second effect, but the core action is immediately legible; no sibling is named explicitly, which keeps it just short of a 5.

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?

Usage is only implied: an agent can infer this applies to a PR currently in the queue, and that queue_pr is the counterpart operation. There is no explicit statement of when to prefer this over alternatives, no precondition ('PR must be queued'), and no note on what happens if it is not queued.

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