Skip to main content
Glama
Sign In
Gizmos Audacity MCP

Gizmos Audacity MCP

by gizmos-quest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Menu

audacity_menu
Destructive

Run Audacity menu commands that need no dialog, such as Play, Stop, Undo, Redo, selection, zoom, track creation, and labels, to automate editing actions.

Instructions

Run a menu command that needs no dialog (Play, Stop, Undo, Redo, SelectAll, SelectNone, NewMonoTrack, NewStereoTrack, NewLabelTrack, AddLabel, ZoomSel, FitInWindow, CursProjectStart, …). Use audacity_transport for guarded recording.

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": {
      "command": "<command>"
    },
    "name": "audacity_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation profile is known; the description's real addition is the "needs no dialog" constraint, which tells the agent why some commands will fail here. It does not disclose that many listed commands (Undo, Delete, RemoveTracks, MixAndRender) irreversibly alter project state, nor whether operations are undoable, so it adds only moderate value beyond the annotations.

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?

One sentence of scope plus one sentence of routing, with the constraint front-loaded before the examples. There is no filler and the alternative tool is named last, which is the right ordering.

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 single-parameter dispatcher with no output schema, the definition covers the essential: what it does, the no-dialog precondition, and where to go for recording. The remaining gap is error behavior (what an agent sees when a command is rejected), which is minor against an enum that enumerates all valid inputs.

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%, but the single parameter is a fully enumerated string, so the valid names are self-documenting. The description repeats a handful of those names without explaining what any command actually does (e.g. SplitNew, SelSave, CursProjectStart), and the trailing ellipsis adds no semantic content. Baseline 3 is appropriate for one enum parameter.

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?

The description gives a specific verb and resource ("Run a menu command") plus a concrete constraint ("needs no dialog") and a representative sample of allowed command names. An agent can immediately tell this is the low-level menu dispatcher. It does not differentiate itself from other generic dispatch siblings, but the menu-command framing is distinct.

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?

It states the selecting condition explicitly (commands that require no dialog) and names one alternative, audacity_transport, for guarded recording. It lacks any statement about what to do when a command does need a dialog, but the primary routing decision is covered.

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