Skip to main content
Glama

redo_change

Restore one of your own undone changes in CopperFlow by default, or a specified undo/change ID. Human undos cannot be redone.

Instructions

Redo one of your own undos: the newest, or the given id (the undo's or the undone change's). A human's undo is theirs; you cannot redo it.

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

Input Schema

NameRequiredDescriptionDefault
idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses ownership scoping (only your own undos), the default target selection, and that human-owned undos are off limits. It omits failure behavior when there is nothing to redo and does not say what is returned, which keeps it below a 5.

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, front-loaded with the core action and default, followed by the ownership caveat. No filler or restatement of the tool name.

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 one-optional-parameter tool with no output schema, the definition covers default behavior, id semantics, and the key permission boundary. Only the no-op/error case and return behavior are unaddressed, which is a minor gap at this complexity.

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 0% for the single optional id parameter, so the description must compensate — and it does: the id may be either the undo's id or the undone change's id, and omitting it selects the newest undo. That is more meaning than the bare string schema provides.

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 (redo) applied to a specific resource (one of your own undos), and immediately describes the two invocation modes: newest-by-default or a given id. It implicitly contrasts with undo_change but never names it, so an agent must infer the pairing rather than being routed explicitly.

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 clear default ('the newest') and the alternative condition ('or the given id'), plus an explicit exclusion: a human's undo cannot be redone. That is real when-to-use and when-not-to-use guidance, though it never names undo_change as the counterpart operation.

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