Skip to main content
Glama
Repository Manager

Repository Manager

Enqueue

rm_merge_queue_enqueue

Enqueue a candidate branch into a repository's serialized merge queue, gate it against the base, then fast-forward the base and optionally prune the worktree and branch.

Instructions

Enqueue (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_enqueue"
  }
}

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

A4/5.0
Behavior5/5

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

Annotations only give coarse hints, and the description adds substantial non-obvious behavior: a repo with no gate declaration is REFUSED, gating is differential against the base ref, an unobtainable baseline refuses rather than allow-alls, lease contention yields deferred:true with the holder, and push failure never fails landing (landed:true/pushed:false with push_error). The dormant prune/delete side effects are also disclosed.

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

Conciseness3/5

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

The opening is front-loaded, but the bulk is general merge-queue doctrine (gate declaration examples across scion-sdk, epistemic-graph, a docs repo; an anecdote about 19 stranded branches) that is only indirectly about calling enqueue. Roughly half the text could move to rm_merge_queue_config or a queue overview without losing anything an agent needs here.

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?

With an output schema present the description needn't enumerate return fields, yet it still explains the outcome semantics (landed vs pushed, deferred, push_error) that matter most. All seven optional params have schema descriptions, and the refusal/lease/differential-gating rules cover the failure modes an agent will actually hit.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still earns credit by explaining the semantic split between 'push' true/false (deferred publication) and by framing repo_path as what makes the queue cross-project with per-repo leases and gate stores. base, prune, and batch_size are covered by the schema rather than the prose.

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 first line names a specific verb and resource ('Enqueue (rm_merge_queue)') and the body makes clear that a candidate branch is handed to a serialized merge queue that gates, fast-forwards the base, and prunes. It never explicitly contrasts itself with the sibling rm_merge_queue_run or rm_merge_queue_withdraw, and in fact the schema's 'reason'/'branch' params describe withdraw behavior, which blurs the boundary between this tool and rm_merge_queue_withdraw.

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?

There is conditional guidance ('Set push false when a scheduler must leave publication to a separate push') and a firm operational rule ('defer, do not retry in a loop' when the lease is held), which is genuinely useful. But there is no statement of when to call this instead of rm_merge_queue_run (the natural follow-on) or rm_merge_queue_withdraw, so the selection decision is left to inference.

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