Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Redo undone changes

clo_redo

Reapply changes just undone by undo, with options to step back multiple edits or force restoration in a different open project. Use before the next project-changing tool call.

Instructions

Reapply changes that clo_undo just undid. Only available until the next tool call that changes the project.

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

Input Schema

NameRequiredDescriptionDefault
forceNoRestore even though CLO now has a different project open than the one the history was recorded in.
stepsNoHow many changes to step over (default 1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add the genuinely non-obvious trait that the redo stack is invalidated by any mutating tool call, which is valuable, but it says nothing about failure behavior when redo is unavailable or what a successful call returns or how state is affected.

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 short sentences, zero filler, with the action front-loaded and the availability constraint immediately after. Every sentence earns its place.

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 two-optional-parameter tool with a fully documented schema and no output schema, the description covers purpose and the critical validity window. Only failure-mode and result-shape details are absent, which is a minor gap given the schema already explains the parameters.

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 both 'force' and 'steps' are already fully documented in the schema, and the description adds nothing about either. Baseline 3 is appropriate when the schema does all the parameter work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('reapply') and resource ('changes that clo_undo just undid'), and explicitly anchors itself to the sibling clo_undo so an agent can pair the two. It stops short of saying what kinds of changes are tracked, but the pairing with clo_undo makes the purpose unambiguous.

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?

Gives a concrete validity window ('Only available until the next tool call that changes the project'), which is the key usage condition an agent must respect. It does not spell out what to do when that window has closed (e.g., fall back to clo_history), so a small piece of routing guidance is missing.

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