Skip to main content
Glama
Sign In
undo

undo

by tathagat22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Undo the last rollback

walkback_redo

Reverses the last rollback by re-applying its reversed changes and re-extending checkpoint history for subsequent rollbacks.

Instructions

Re-apply the changes that the most recent walkback_rollback reversed, and re-extend the history so you can roll back again.

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

Input Schema

NameRequiredDescriptionDefault
cwdNoProject directory. Defaults to the server's working directory.

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?

No annotations provided, so description bears full burden. It discloses the action (re-apply, re-extend history) but lacks details on destructive potential, idempotency, prerequisites (e.g., a prior rollback), or error handling.

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?

One sentence, no redundancy, front-loaded with key action. Every phrase adds value.

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 low complexity (1 optional param, no output schema) and no annotations, the description is fairly complete. It explains core behavior and context but omits edge cases and results.

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 covers the single parameter cwd with a description; the tool description adds no extra semantic meaning beyond that. Baseline 3 is appropriate.

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 clearly states the verb (Re-apply) and resource (changes from the most recent walkback_rollback), distinguishing it from siblings like walkback_rollback and walkback_revert by specifying it undoes the last rollback.

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?

Description implicitly tells when to use: after a rollback. It also mentions re-extending history for further rollbacks, providing context. However, it does not explicitly exclude cases (e.g., when no rollback exists) or compare with alternatives.

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