Skip to main content
Glama

Apply a merge plan

argon_merge_apply
Destructive

Applies a pending merge plan to an isolated MongoDB sandbox; for conflicted plans, specify strategy 'theirs' to take the branch or 'ours' to keep the target.

Instructions

Apply a pending merge plan. Conflicted plans need a strategy: theirs (take the branch) or ours (keep the target).

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": {
      "plan_id": "<plan_id>"
    },
    "name": "argon_merge_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesPlan ID from argon_merge_preview
strategyNoConflict resolution: theirs or ours

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds one genuinely new behavioral fact — that conflicted plans require an explicit strategy — but says nothing about irreversibility, whether the plan is consumed on success, or what happens to the working tree on failure, which matters for a destructive, non-idempotent operation.

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?

Two sentences, front-loaded with the action and followed by the one conditional the agent must handle. No filler, no repetition of the title or of schema-declared types.

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

Completeness3/5

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

For a two-parameter mutation with full schema coverage and annotations covering safety, the description covers the core decision (which strategy) but omits outcome information: no mention of what a successful apply produces, whether the plan ID becomes invalid, or how partial/failed merges are left. No output schema exists, so those return-side expectations go unaddressed.

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, and the description earns above that by defining the ambiguous enum values: theirs means take the branch, ours means keep the target. That disambiguation is the single most useful piece of semantic information for this tool and is absent from the schema, which only says "theirs or ours".

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 ("Apply a pending merge plan") and links backward to the sibling that produces the input, via "Plan ID from argon_merge_preview". It is clearly a mutation of an existing plan rather than a preview or branch listing, though it never explicitly says "use argon_merge_preview first".

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?

The second sentence gives conditional guidance: a strategy is required only for conflicted plans, which is real when-to-use information. However, it offers no exclusions or alternatives (e.g. when to re-run preview instead of applying, or what to do if the plan is stale), leaving the agent to infer the prerequisites.

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