Skip to main content
Glama

undo_change

Revert your newest change or a specific change by id, restoring the prior PCB design state. Use it to roll back an edit you made; human redo actions stay theirs.

Instructions

Undo one of your own changes: the newest, or the given id. A human's "Redo:" of it is theirs; you cannot undo 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": "undo_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoe.g. c0003

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses ownership scope and the limitation around human Redo actions, but it does not explain what happens to history, whether an undo can itself be undone, or how failures are handled.

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?

The description is two short sentences, front-loaded with the action and scope. Every sentence contributes: the first explains what can be undone, and the second clarifies the human Redo boundary.

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 simple one-optional-parameter tool with no output schema, the description covers the essential scope and the main ownership constraint. It is not exhaustive about edge cases such as invalid ids or undo history behavior, but it is adequate for correct invocation.

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 already 100%, so the baseline is 3. The description adds meaningful semantics by explaining that the id selects a given change and that omitting it targets the newest change, which goes beyond the schema's example value.

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 states a specific verb and resource: undo one of your own changes, either the newest or a given id. It also distinguishes ownership scope by noting that a human's Redo is theirs and cannot be undone, which helps separate this from redo_change.

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?

The description gives clear usage context: call it to undo your own change, with no id for the newest or with an id for a specific change. It also states a key exclusion: you cannot undo a human's Redo of it. It does not explicitly name redo_change as the alternative, but the intended use is clear.

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