Skip to main content
Glama

History

audacity_history
Destructive

Undo or redo native Audacity menu/import history entries by a given step count, halting safely when an entry is missing or Audacity reports an error.

Instructions

Undo or redo existing native menu/import history entries. Individual scripted effects and pipelines add no undo entry; save a project backup before destructive processing. Stops before a step the native history does not have, or at Audacity’s own first error, and does not claim checkpoint rollback.

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": {
      "action": "<action>"
    },
    "name": "audacity_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsNo
actionYes

Output Schema

NameRequiredDescriptionDefault
actionYes
completedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false, non-idempotent), the description discloses partial-failure semantics: execution halts before a step missing from native history or at Audacity's first error, and it explicitly disclaims checkpoint rollback. It also states the data-loss risk and the required mitigation (backup first). This is exactly the extra context annotations cannot convey.

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?

Three dense sentences, front-loaded with the core action and followed by preconditions and failure behavior; almost no filler. The phrase "does not claim checkpoint rollback" is slightly opaque and could be stated more plainly, which costs a point.

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?

Given a destructive two-parameter mutation with an output schema and full annotations, the description covers risk, preconditions, and partial-failure behavior well. The notable remaining gap is the meaning and limits of the "steps" parameter, which neither the schema nor the description explains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, and it largely does not. The "steps" parameter (integer, default 1, max 100) is never explained as a count of history entries to traverse; the word "step" appears only in the failure-semantics sentence. Only "undo/redo" is conveyed, and that already comes from the enum.

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?

"Undo or redo existing native menu/import history entries" is a specific verb plus a narrowly scoped resource (native menu/import history, not scripted effect commands). It also implicitly separates this tool from audacity_effect/audacity_pipeline by stating those add no undo entry. It stops short of naming a sibling tool outright, so it is clear but not maximally differentiating.

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 establishes the context of use (reverting native menu/import actions) and effectively warns that scripted effects and pipelines are out of scope for undo, which functions as a when-not-to-use signal. It gives a prerequisite ("save a project backup before destructive processing"). It does not explicitly compare against alternatives such as audacity_edit or audacity_menu, which keeps it from a 5.

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