Gizmos Audacity MCP

Overview Schema Source Related Servers Discussions Admin

Effect

audacity_effect

Destructive

Select a track or range and apply bundled Audacity effects with catalogue parameters; defaults to track extent to avoid silent gaps.

Instructions

Select a track/range and apply an effect using the bundled English Audacity 3.7.8 catalogue parameters. Default time scope is the track extent, avoiding silent gap clips. NoiseReduction requires a captured profile on this same track and params={}; it uses saved UI settings. Scripted effects add no undo entry: save a project backup first.

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": {
      "effect": "<effect>"
    },
    "name": "audacity_effect"
  }
}

Input Schema

Name	Required	Description
`end`	No
`start`	No
`track`	No	track index (0-based) or unique track name
`effect`	Yes
`params`	No
`trackCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already flag destructive=true and idempotent=false, and the description adds information annotations cannot convey: scripted effects create no undo entry, so a backup is required. The NoiseReduction profile dependency and the 'saved UI settings' behavior are also non-obvious operating characteristics disclosed up front.

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?

Four tightly packed sentences, front-loaded with the selection-and-apply action before the caveats. Every sentence carries operational weight, though the density of clauses in the middle sentences makes it slightly harder to scan.

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?

Covers destructiveness, undo loss, prerequisites, and scope defaults for a 6-parameter tool with a nested free-form params object and no output schema. Remaining gaps are the undocumented trackCount and the absence of any concrete params key example or pointer to a discovery tool.

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 coverage is only 17% (just the track field), and the description partially compensates: it explains that params keys are the English Audacity 3.7.8 catalogue parameters, that default time scope is the track extent for start/end, and that NoiseReduction takes params={}. However, it never explains trackCount, gives no example params keys, and offers no discovery path for valid parameter names.

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+resource ('apply an effect' to a 'track/range') and scopes it to the 'bundled English Audacity 3.7.8 catalogue', which tells an agent this is the generic effect entry point. It does not name specialized siblings like audacity_fade or audacity_auto_duck, so the boundary with those is left implicit.

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?

Gives concrete preconditions: default time scope is the track extent, NoiseReduction requires a previously captured profile on the same track with params={}, and a project backup should be saved first. It lacks explicit when-to-use-this-instead-of guidance versus sibling effect tools such as audacity_fade or audacity_auto_duck.

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

Deploy Server