Skip to main content
Glama
Sign In
Gizmos Audacity MCP

Gizmos Audacity MCP

by gizmos-quest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Quit

audacity_quit
Destructive

Closes Audacity on Windows without a save prompt, optionally preserving the project at a specified .aup3 path; omit saveTo to discard the project.

Instructions

On Windows, quit Audacity without a save prompt. Without saveTo the project is discarded (saved to a temporary file that is then deleted).

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_quit"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveToNokeep the project at this .aup3 path

Output Schema

NameRequiredDescriptionDefault
savedToNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds real value on top: what actually happens to unsaved work (written to a temp file, then deleted) and that no save prompt appears. The 'On Windows' qualifier is ambiguous, leaving it unclear whether the no-prompt/discard behavior applies on other platforms.

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 short sentences with the platform caveat and the destructive-default spelled out up front; nothing is redundant. The leading 'On Windows' phrase is the weakest element because it is not resolved anywhere in the definition.

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?

An output schema exists so return values need not be described, and the single parameter is fully covered. For a destructive, non-idempotent quit tool the definition covers the main risk; only the platform scope of the no-prompt behavior and the effect of calling it when no session is running are left open.

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 100% and the schema already defines saveTo as an .aup3 path to keep the project at. The description adds the missing half of the semantics — that omitting saveTo means the project is discarded — which is exactly the decision-relevant meaning an agent needs.

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 and resource ('quit Audacity') plus the key condition that no save prompt is shown. It is clearly distinguishable from siblings that launch, reset, or edit a project, though it never names a sibling explicitly.

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?

The description implies the end-of-session use case and explains the consequence of omitting saveTo, which helps an agent decide. It gives no explicit when-to-use/when-not-to-use guidance and does not contrast with alternatives such as audacity_fresh or audacity_launch.

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

Deploy Server

Other Tools