Skip to main content
Glama

Record how to reverse a cloud/DB action

walkback_record_reversal

Record the command that reverses actions on external systems (cloud, databases) for later execution with dry-run gating.

Instructions

Record the command that reverses something the agent did to an external system — a cloud resource (e.g. 'terraform destroy', 'aws s3 rb s3://bucket') or a database change (e.g. an inverse SQL via psql). walkback_compensate will run it (dry-run gated). Works with any tool. For UPDATE/DELETE you must capture the prior values to build the inverse — walkback runs what you give it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoProject directory. Defaults to the server's working directory.
runInNoDirectory to run the command in. Defaults to the project.
commandYesThe command that reverses it, e.g. 'aws s3 rb s3://assets-prod'.
descriptionYesWhat was done, e.g. 'created S3 bucket assets-prod'.
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses recording behavior and relationship to compensation tool, but does not detail validation, persistence, or side effects of recording. Adequate but not thorough.

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?

Concise single paragraph with front-loaded purpose, examples, and relation to sibling. No redundant sentences, but could be slightly better structured with bullet points.

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?

Explains role in walkback system and gives use-case examples. However, does not address multiple recordings, overwrites, or persistence duration. For a recording tool, this is a gap.

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 baseline 3. Description adds value with concrete examples for command and description parameters, plus guidance on capturing prior values for updates/deletes. Exceeds baseline.

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?

Description clearly states verb ('Record') and resource ('command that reverses something'), with specific examples (terraform destroy, aws s3 rb, inverse SQL). Distinguishes from sibling walkback_compensate by noting it will run the recorded command.

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?

Explicitly relates to walkback_compensate (dry-run gated) and gives when-to-use guidance for UPDATE/DELETE requiring prior values. Lacks explicit when-not-to-use scenarios but is clear enough.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tathagat22/walkback'

If you have feedback or need assistance with the MCP directory API, please join our Discord server