Skip to main content
Glama
Sign In
undo

undo

by tathagat22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Full walkback history

walkback_log

Review a chronological list of all checkpoints and effects recorded by the undo server to understand changes to files and network state.

Instructions

List every checkpoint and effect in order.

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_log"
  }
}

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

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only says 'list in order' but does not mention read-only nature, permissions needed, or side effects. For a list operation, agents need to know if it is safe.

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

Conciseness4/5

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

The description is a single concise sentence that gets to the point. It could be slightly more informative without adding much length, but it is efficient.

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

Completeness2/5

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

Given the tool has no output schema, no annotations, and many siblings, the description is too minimal. It does not explain return values, ordering specifics, or behavior differences from similar tools like walkback_status.

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?

The input schema has 100% coverage with a single parameter 'cwd' described. The tool description adds no extra meaning beyond what the schema provides. Baseline score of 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 'List every checkpoint and effect in order,' providing a specific verb and resource. It distinguishes the tool from siblings like walkback_checkpoint or walkback_status by indicating it returns the full history.

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 description implies the tool is for listing history, but it does not explicitly state when to use this tool versus alternatives like walkback_status or walkback_diff. No exclusions or when-not-to-use guidance is provided.

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