Skip to main content
Glama

history

Destructive

Undo or redo the latest Step Studio change by one entry, including edits from any user. Use restore for changes older than the undo stack.

Instructions

Step Studio's own undo history back or forward one entry, exactly like Ctrl+Z or Ctrl+Y. It affects the latest change by anyone, including the user, not only Tufan's. Each Tufan write (and each batch, create_tree or mass_edit) is one entry. For anything older than the undo stack, use restore (snapshots) or restore_from_mirror.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "direction": "<direction>"
    },
    "name": "history"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.
directionYes"undo" reverts the latest change; "redo" re-applies the last undone one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / direction / description
      Added value: +"\"undo\" reverts the latest change; \"redo\" re-applies the last undone one."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructive=true and non-idempotent, and the description adds real context: it affects the latest change by anyone (not only Tufan's), and each Tufan write, batch, create_tree or mass_edit counts as one entry. It leaves the stack-edge behavior (what happens when there is nothing left to undo or redo) unstated, which is the main residual gap.

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?

Three short sentences, front-loaded with the action and its familiar analogy, followed by scope and then the fallback tools. No sentence is filler.

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 destructive two-parameter mutation with annotations and no output schema, the description covers granularity, scope of affected change, and alternatives. Edge cases such as an empty undo/redo stack or whether the place must be open are not addressed, so it falls just short of complete.

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 coverage is 100% and the enum values are already documented there, so the description only reinforces what direction and place mean without adding syntax or defaults. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

Names a specific verb and resource ("undo history back or forward one entry") and anchors it with the Ctrl+Z/Ctrl+Y analogy. It also scopes the operation to Studio's own undo stack, which is what separates it from restore and restore_from_mirror.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use (revert/re-apply the latest change) and when-not-to-use, naming restore (snapshots) and restore_from_mirror for anything older than the undo stack. The agent has no inference left to do.

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