Skip to main content
Glama

Undo a range of history

argon_undo
Destructive

Revert a branch history range so every touched document returns to its prior state, optionally limited to one actor; preview changes with dry_run before applying.

Instructions

Revert a range of a branch's history: every touched document returns to its state before the range. Optionally restricted to one actor's writes. Use dry_run to preview.

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": {
      "project": "<project>",
      "branch": "<branch>",
      "from_lsn": "<from_lsn>"
    },
    "name": "argon_undo"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorNoOnly revert writes by this actor
branchYesBranch name
to_lsnNoEnd of the range (default: branch head)
dry_runNoPreview without applying
projectYesProject name
from_lsnYesStart of the range to revert

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.1

TDQS

A4/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 describing blast radius ('every touched document returns to its state before the range') and by surfacing dry_run as a non-destructive escape hatch. It stops short of saying whether the revert itself is recoverable or what happens on conflicts.

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 with no filler: the primary effect comes first, then the optional scoping and preview note. Every clause carries information.

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 destructive, six-parameter mutation with no output schema, the description covers effect, scope and preview. It leaves open recovery after the revert and required permissions, but annotations already flag destructiveness, so the remaining gap is modest.

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 branch, from_lsn, to_lsn, actor and dry_run. The description confirms actor scoping and dry_run's purpose but adds no format, boundary or default detail (e.g. whether to_lsn is inclusive) beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Revert a range of a branch's history') plus the concrete outcome ('every touched document returns to its state before the range'). The scope (range-based, multi-document) distinguishes it from single-item operations and from the merge/diff siblings without ambiguity.

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?

Gives actionable guidance for two modes: narrowing to a single actor's writes and previewing with dry_run. It never names when NOT to use it or points at alternatives such as argon_diff or argon_merge_preview for inspection, so routing relies on the agent's own inference.

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