Skip to main content
Glama
Sign In
Gizmos Audacity MCP

Gizmos Audacity MCP

by gizmos-quest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Launch

audacity_launch

Start or attach to Audacity with a visible or hidden Windows window, then wait for a verified script-pipe response before continuing audio automation.

Instructions

Start or attach to Audacity with a visible or hidden Windows project window. Waits for a real script-pipe response.

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

Input Schema

NameRequiredDescriptionDefault
visibleNo

Output Schema

NameRequiredDescriptionDefault
startedYes
visibleYes
processesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true and readOnlyHint=false, so the agent knows this touches an external process. The description adds genuinely new behavioral facts: it blocks until a real script-pipe response arrives, and it can run the app with a hidden window. It does not say what happens if an instance is already running, whether it is safe to call repeatedly (relevant given idempotentHint=false), or what permissions/installation it assumes.

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 primary action front-loaded and no filler. "Waits for a real script-pipe response" is slightly jargon-heavy but earns its place as the key blocking behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter bootstrap tool with an output schema (so return values need not be explained), the description covers action, blocking behavior, and window mode. It omits the already-running case, failure conditions (Audacity not installed / non-Windows host), and whether repeated calls are safe.

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?

Only one parameter exists and schema description coverage is 0%, so the description must carry the weight. "Visible or hidden Windows project window" maps the `visible` flag to a concrete effect on the launched app, which the bare boolean schema does not convey. It stops short of clarifying the default or what "hidden" implies for control flow.

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 pair ("Start or attach") and resource (Audacity), plus the scope of the window mode. An agent knows this bootstraps/connects the app rather than manipulating audio. It does not explicitly contrast itself with the closest sibling (audacity_fresh) or say how "attach" differs from "start".

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?

"Start or attach" implies the precondition (Audacity not yet running or needing a connection), which is useful implicit guidance. There is no explicit when-to-use/when-not statement and no pointer to an alternative tool for restarting or resetting a session.

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