Gizmos Audacity MCP

Overview Schema Source Related Servers Discussions Admin

Fade

audacity_fade

Destructive

Apply a sample FadeIn or FadeOut to a specific track and time range; omit start and end to fade the full track extent, or use envelope automation for editable changes.

Instructions

Apply sample FadeIn or FadeOut on one track and time range. Omitting time applies to the track extent; use envelope_set for editable automation.

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": {
      "track": "<track>",
      "direction": "<direction>"
    },
    "name": "audacity_fade"
  }
}

Input Schema

Name	Required	Description	Default
`end`	No
`start`	No
`track`	Yes
`direction`	Yes

Output Schema

Name	Required	Description	Default
`end`	Yes
`start`	Yes
`track`	Yes
`direction`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the mutation profile is covered. The description adds useful default-range behavior and an alternative route, but doesn't say whether the fade is applied in place to audio data, whether it is undoable, or what happens when start/end fall outside existing audio.

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?

Two tight sentences with zero padding: the core action comes first, then the default-range rule, then the pointer to the alternative. Every clause carries information an agent needs.

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?

An output schema exists, so return values need no explanation, and annotations cover safety. Still, for a destructive 4-parameter mutation with 0% schema description coverage, the definition leaves time units and track identification unaddressed, which an agent needs to call it correctly.

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 the load, and it only partially does: it implies track, start/end and the in/out direction mapping. It never states the units for start/end (apparently seconds, capped at 86400) or whether track accepts an index, name, or both, despite the schema allowing either.

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: apply a FadeIn/FadeOut to one track over a time range, and explicitly contrasts with envelope_set for editable automation, so an agent can distinguish it from the sibling. The phrase "sample Fade" is slightly imprecise about what is actually being modified, which keeps it from a 5.

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 a concrete default rule (omitting the time range applies to the whole track extent) and names an alternative (envelope_set) for when editable automation is wanted. It stops short of explicit when-not conditions, such as whether it works on selections or multiple tracks.

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

Deploy Server