Skip to main content
Glama

effect_auto_duck

Automatically lower a selected track's volume whenever audio is detected on an above control track, with adjustable fades and threshold for narration-over-music mixing.

Instructions

Auto Duck: automatically reduce volume when audio is detected on another track. Place the control track (e.g. narration) above the track to duck (e.g. music). Select the track to duck before running.

Args: duck_amount_db: How much to reduce volume in dB (-24 to 0). Default: -12 inner_fade_down_len: Inner fade down length in seconds (>= 0). Default: 0 inner_fade_up_len: Inner fade up length in seconds (>= 0). Default: 0 outer_fade_down_len: Outer fade down length in seconds (>= 0). Default: 0.5 outer_fade_up_len: Outer fade up length in seconds (>= 0). Default: 0.5 threshold_db: Threshold for duck trigger in dB (-100 to 0). Default: -30 maximum_pause: Maximum pause between ducking regions in seconds (>= 0). Default: 1.0

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threshold_dbNo
maximum_pauseNo
duck_amount_dbNo
inner_fade_up_lenNo
outer_fade_up_lenNo
inner_fade_down_lenNo
outer_fade_down_lenNo
Install Server

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are present, so the description carries the full behavioral burden. It discloses the trigger mechanism, control-track placement, and selection requirement, but it does not state whether the effect is destructive/undoable, how the control track is treated, or what the resulting output will be.

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?

The description is compact and well-organized: purpose, setup steps, then a single Args block. It front-loads the core behavior, avoids redundant prose, and every line contributes useful information.

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 7-parameter optional effect with no annotations or output schema, the description covers the core operation, all parameter semantics, and required setup. The main gap is the lack of detail about reversibility and the exact scope of modification (track vs. clip), which leaves a small but non-fatal ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All seven parameters are documented in the Args block with meanings, ranges, and defaults, fully compensating for the 0% schema description coverage. For example, threshold_db is explained as 'Threshold for duck trigger in dB (-100 to 0)' rather than being left as a bare numeric property.

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 description opens with a specific verb and resource: 'automatically reduce volume when audio is detected on another track.' This clearly identifies the sidechain-ducking behavior and separates it from other effect tools like amplify or fade without requiring schema inspection.

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?

The description provides concrete usage context: place the control track above the track to duck and select the target track before running. It does not explicitly name alternatives or when-not conditions, but the intended use case is clear enough for an agent to select this tool over sibling effects.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FFriends/MCP-Audacity'

If you have feedback or need assistance with the MCP directory API, please join our Discord server