Skip to main content
Glama
Sign In
undo

undo

by tathagat22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Selectively undo one file

walkback_revert

Reverse the most recent change to a specific file, preserving all other modifications since the checkpoint.

Instructions

Reverse just a single file (the most recent change to it), leaving every other change since the checkpoint in place. The opposite of rollback's all-or-nothing.

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": {
      "path": "<path>"
    },
    "name": "walkback_revert"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoProject directory. Defaults to the server's working directory.
pathYesThe file to revert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that other changes remain intact, but does not explain side effects like whether the reversal is tracked as a new change, required permissions, or edge cases (e.g., file unchanged).

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, zero wasted words, action verb first, efficient.

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?

Given the tool's simplicity and lack of output schema, the description covers the core behavior. Missing details about return value and edge cases, but overall sufficient for its purpose.

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 coverage is 100% with descriptions for both parameters. The description adds no further parameter details beyond the schema, so it meets the baseline but doesn't exceed it.

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?

The description uses specific verbs ('reverse just a single file') and resources ('most recent change'), and explicitly contrasts with rollback, making the tool's distinct purpose clear.

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?

The description states when to use this tool (selective undo) vs. rollback (all-or-nothing), providing clear context. However, it doesn't mention prerequisites like needing a checkpoint or behavior when the file has no changes.

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