Skip to main content
Glama
Repository Manager

Repository Manager

Status

rm_merge_queue_status
Read-onlyIdempotent

Reports the current merge-queue status for any Git repository, including lease holder, candidate outcomes, and landed versus pushed state so you can decide when to enqueue or defer.

Instructions

Status (rm_merge_queue). Serialized merge queue for ANY git repository (CONCEPT:RM-MERGE-QUEUE).

The canonical driver of parallel development: lanes take worktrees, work, then hand branches here, and the queue gates them as merged, fast-forwards the base, and prunes the worktree and branch. Set push false when a scheduler must leave publication to a separate push.

The queue does not know what a gate is. Gates are declared in the target repository's own .mergequeue.yaml — a command, a tier, a timeout, and how to compare its result against the base ref. scion-sdk declares pytest + ruff + its contract scripts; epistemic-graph declares cargo check --all-features + clippy; a docs repo could declare only a link check. A repository with no declaration is REFUSED rather than defaulted, because "declared no gates" and "has no queue configured" must not be the same value.

Gating is differential: only a failure the base ref does not already produce blocks a candidate — the base is legitimately red here, and an absolute gate once deadlocked a queue and stranded 19 branches. A baseline that cannot be produced REFUSES the candidate; it never degrades to allow-all.

run holds that repository's reconciliation-merge LEASE. If another runner holds it the call returns deferred: true with the holder — defer, do not retry in a loop.

landed vs pushed (D-W3WPS-3). Each outcome carries both, separately: landed means the declared base ref fast-forwarded in the LOCAL canonical checkout (proven by re-reading it); when push is true, pushed means that commit also reached the configured remote via the repo's own gated push path (_gate_before_push + push_project — the same pre-commit gates and GH013/divergent-remote handling a manual push gets). With push false, publication is deliberately deferred to a separate push. A push failure never fails the landing — landed: true, pushed: false is a legitimate, visible intermediate state; check push_error on the outcome for why. The queue's own run summary also reports pushed/landed_unpushed counts.

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

Input Schema

NameRequiredDescriptionDefault
baseNoBranch to land onto. Defaults to the repo's declared base.
pushNoPublish a landed base through the repository's gated push path. Set false for the fast queue timer; publication is then a separate, explicit push.
pruneNoRemove each landed candidate's worktree and branch through the guarded prune (merge-base re-checked at delete time, a refs/lane-backup anchor written first, `git branch -d` never -D, and a worktree holding uncommitted work is refused).
branchNoCandidate branch for enqueue/withdraw. Defaults to that tree's HEAD.
reasonNoWhy a candidate is being withdrawn.
repo_pathNoAny working tree of the target repository. This is what makes the queue cross-project: one server, N repositories, each with its own lease, candidate store, and gates. Defaults to the server's cwd.
batch_sizeNoCandidates gated together per run (0 = the repo's declared batch_size).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.7
    • changedInput schema / properties / push / description
      Previous value: -"Publish a landed base through the repository's gated push path. Set false for the fast queue timer; the phased-push scheduler then owns publication."New value: +"Publish a landed base through the repository's gated push path. Set false for the fast queue timer; publication is then a separate, explicit push."
  2. First observedv3.5.1

TDQS

C2/5.0
Behavior1/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, but the description describes gateway mutation: fast-forwarding the base ref, removing worktrees and branches via prune, and publishing commits to a remote, plus parameters (`push`, `prune`) defaulting to true that would trigger exactly those writes. This is a direct conflict between the claimed read-only profile and the documented behaviour.

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

Conciseness2/5

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

Five dense paragraphs with heavy bold, double-backtick artifacts, a D-W3WPS-3 reference, and war stories ('an absolute gate once deadlocked a queue and stranded 19 branches'). The most important fact, what the tool returns, is buried; the front-loaded material is system design, not the call's contract.

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?

An output schema exists and there are no required parameters, so the description needn't explain return values, yet it spends its length on queue philosophy and omits the essentials: what status returns, whether it mutates anything, and how it relates to the run/enqueue/withdraw siblings. For a tool whose annotations already conflict with the prose, the description fails to resolve the ambiguity an agent needs resolved.

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 description coverage is 100%, so the schema already explains base, push, prune, branch, reason, repo_path, and batch_size. The description adds some value by explaining the `landed` vs `pushed` split, the `push_error` outcome, and the lease-deferral response with its holder, but it does not clarify the parameters that are genuinely ambiguous here, such as `branch`/`reason` (enqueue/withdraw fields) on a Status tool.

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

Purpose2/5

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

The opening line 'Status (rm_merge_queue). Serialized merge queue for ANY git repository' restates the name and then explains the merge-queue concept rather than what this specific call does. It never says what status actually reports back, and the described behaviour (landing, fast-forwarding, pruning, pushing) reads like rm_merge_queue_run rather than a Status tool, so the agent cannot distinguish it from its sibling.

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 statement of when to call this tool instead of rm_merge_queue_run, rm_merge_queue_enqueue, rm_merge_queue_withdraw, or rm_merge_queue_config, even though all four are siblings in the same family. The only guidance given ('defer, do not retry in a loop') concerns handling a deferred response, not tool selection.

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

Deploy Server

Other Tools