Skip to main content
Glama

Recover

audacity_recover
Destructive

Inspect Audacity process, pipe, and crash-recovery state; close blocking dialogs, reconnect after a timeout, or clear stale recovery entries without killing Audacity or replaying edits.

Instructions

Inspect process, pipe and crash-recovery entries; optionally close blocking dialogs and reconnect after a timeout. Never kills Audacity or replays edits. discardRecovery clears stale config entries only while Audacity is stopped, saving the config first and retaining all project files.

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

Input Schema

NameRequiredDescriptionDefault
visibleNo
reconnectNo
closeDialogsNo
discardRecoveryNo

Output Schema

NameRequiredDescriptionDefault
noteNo
tracksNo
entriesYes
runningYes
windowsYes
discardedYes
synchronizedNo
needsRecoveryNo
previousOutcomeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description adds real specificity on top: it never kills Audacity or replays edits, and discardRecovery saves the config first and retains all project files. That materially narrows what 'destructive' means here, though it does not describe what a successful response contains or side effects of closing dialogs.

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?

Two dense sentences with no filler and the safety guarantees front-loaded. The telegraphic opening ('Inspect process, pipe and crash-recovery entries') is compact but slightly terse for a first read.

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?

With an output schema present, return values need not be explained, and the destructive-path preconditions are covered. The remaining gap is the undocumented 'visible' parameter and the absence of guidance on what to do after a failed recovery attempt.

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 0%, so the description must carry all four parameters. It explains discardRecovery thoroughly and implies closeDialogs and reconnect through 'close blocking dialogs' and 'reconnect after a timeout', but the 'visible' flag is never explained anywhere, leaving one of four parameters undocumented.

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 specific verbs and resources: 'Inspect process, pipe and crash-recovery entries' plus optional dialog-closing and reconnection. It is distinguishable from pure inspection tools like audacity_dialogs, though it does not name a sibling for the pure-dialog path.

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

Usage Guidelines3/5

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

Gives a precondition for the risky path ('discardRecovery ... only while Audacity is stopped') and frames dialogs/reconnect as optional recovery steps, which implies when to use it. It never states when to prefer a sibling such as audacity_dialogs or audacity_launch instead.

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