Gizmos Audacity MCP

Overview Schema Source Related Servers Discussions Admin

Clip Set

audacity_clip_set

Destructive

Rename or recolor an audio clip, or apply a destructive relative gain in dB to its samples by targeting a point inside one clip away from boundaries.

Instructions

Rename/color a clip or apply a relative gain in dB destructively to its samples. For name/color, at must lie strictly inside exactly one clip, avoiding shared boundaries. Use audacity_track_set gainDb for a reversible track slider, audacity_clip_move for timing.

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>",
      "at": "<at>"
    },
    "name": "audacity_clip_set"
  }
}

Input Schema

Name	Required	Description
`at`	Yes	time inside the clip; name/color require a point strictly after its start and before its end
`name`	No
`color`	No
`track`	Yes
`gainDb`	No	relative sample gain applied destructively with Amplify to this clip

Output Schema

Name	Required	Description	Default
`end`	Yes
`name`	No
`color`	No
`start`	Yes
`track`	Yes
`gainDbApplied`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description corroborates and explains them by saying the gain is applied 'destructively to its samples' and is 'relative', which is why repeated calls compound. It does not cover undo/reversibility of the gain path or the boundary-failure behavior when a point spans two clips, so it stops short of full transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, no filler, with the destructive caveat and the alternative tools front-loaded where they matter. Nothing is wasted and the structure puts the negative guidance before the constraint detail.

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 and annotations cover the safety profile, so the description needn't explain return values or risk. Given a mutation tool with five parameters, the remaining gap is the unexplained `track` identifier format and the failure mode at clip boundaries, which would matter for correct invocation.

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?

With only 40% schema coverage, the description carries real weight: it clarifies that gainDb is relative and destructive, and it adds a constraint for `at` beyond the schema's wording — the point must fall inside exactly one clip and avoid shared boundaries. The `track` parameter (accepts integer or string) remains unexplained in both description and schema, preventing a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names specific verbs (rename, color, apply relative gain in dB) against a specific resource (a clip) and even states the destructive nature of the gain path. An agent can distinguish this from audacity_clip_move or audacity_track_set without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent away: audacity_track_set gainDb for a reversible track-level slider, audacity_clip_move for timing. It also states the precondition for the name/color path (the point must lie strictly inside exactly one clip, avoiding shared boundaries), which is exactly the when-to-use/when-not-to-use information an agent needs.

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

Deploy Server