Skip to main content
Glama

merge_ready

Check if a pull request can merge by verifying review approval, CI status, and project guardrails, and get clear reasons for each blocker.

Instructions

May this pull request merge? One answer from the review gate, CI and the guardrails of the project its ticket belongs to. pr is a PR URL or owner/repo#12. Returns ready (true only when the PR is open, not a draft, the review gate approved its current head, CI passed or the project has none, and no guardrail blocks), reasons (a sentence for each thing holding the merge back; empty when ready), the head commit, and the review, ci and guardrails answers. A bad reference, a PR no ticket has or a failed read comes back as ready false with a reason. It changes nothing: it only answers; Tares's merge queue does the merging. project is accepted for consistency with the other tools; the project comes from the pull request's ticket.

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": {
      "pr": "<pr>"
    },
    "name": "merge_ready"
  }
}

Input Schema

NameRequiredDescriptionDefault
prYes
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does: it declares the tool changes nothing, defines the precise conditions under which ready is true, and states that bad references, unticketed PRs, or failed reads return ready false with a reason. That is a complete behavioral contract.

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?

Front-loaded with the core question and the ready conditions, with no filler sentences. The paragraph is dense and the final project caveat is tacked on with a slightly awkward run-on, which costs a point.

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

Completeness5/5

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

Even though an output schema exists, the description sketches the return shape (ready, reasons, head commit, and the three gate answers) and covers error paths, so an agent knows both what it gets and how failures appear. Nothing material is missing for a two-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description compensates fully: `pr` accepts a PR URL or `owner/repo#12`, and `project` is accepted only for consistency while the real project is derived from the PR's ticket. Both parameters gain meaning the schema does not provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with the exact question the tool answers ('May this pull request merge?') and enumerates the three gates (review, CI, guardrails) it consults. That gives a specific verb-plus-resource identity distinct from readers like get_ticket or read.

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?

Makes the usage boundary clear by stating it only answers and that 'Tares's merge queue does the merging', so an agent knows not to call it expecting a merge. It lacks an explicit named alternative for actually merging, which keeps it short of a 5.

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