Skip to main content
Glama
Audionaut MCP Server

Audionaut MCP Server

Set clip fades

clip_fades

Sets the addressed clip's fade ramps and curve exponents (0.1-4, 0.5 = equal power). All four fade values are in unit (default bars) and 0 clears one.

Instructions

Sets the addressed clip's fade ramps and curve exponents (0.1-4, 0.5 = equal power). All four fade values are in unit (default bars) and 0 clears one. Each ramp has two edges measured inward from the clip edge: the fade-in runs from fade_in_start to fade_in after the clip start, the fade-out from fade_out to fade_out_end before the clip end, so a ramp lasts fade_in - fade_in_start (or fade_out - fade_out_end). A negative offset puts that edge outside the clip, playing source audio beyond it - e.g. fade_out 0.25 with fade_out_end -0.25 (seconds) is a 0.5 s ramp centred on the clip end, the outgoing half of a crossfade. Values are clamped against each other within the clip. The address must match exactly one clip.

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": {
      "project": "<project>"
    },
    "name": "clip_fades"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoTimeline position of the clip (exclusive with region)
taskNoName of the task this edit is part of, e.g. "remove speech pauses". In the open app, all edits with the same task name become one undo step: keep the name for every call of the task and change it when the next task starts. Without a task name, all edits of this session share one step
unitNoUnit for positions (default bars; bars/beats are 1-based, seconds/clocks absolute)
trackNoTrack id
regionNoRegion name of the clip
fade_inNoWhere the fade-in ramp reaches full level, measured from the clip start; the ramp length only when fade_in_start is 0
projectYesPath to the .audium project package (absolute paths recommended)
fade_outNoWhere the fade-out ramp begins, measured back from the clip end; the ramp length only when fade_out_end is 0
fade_out_endNoWhere the fade-out ramp reaches silence, measured back from the clip end; negative = past the clip end
fade_in_curveNoFade-in curve exponent (0.1-4, 0.5 = equal power)
fade_in_startNoWhere the fade-in ramp begins, measured from the clip start; negative = before the clip start
fade_out_curveNoFade-out curve exponent (0.1-4, 0.5 = equal power)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.7
    • addedInput schema / properties / task
      Added value: +{
      +  "description": "Name of the task this edit is part of, e.g. \"remove speech pauses\". In the open app, all edits with the same task name become one undo step: keep the name for every call of the task and change it when the next task starts. Without a task name, all edits of this session share one step",
      +  "maxLength": 80,
      +  "type": "string"
      +}
  2. Changed4 schema fields changedv1.6.4
    • changedInput schema / properties / fade_in / description
      Previous value: -"Fade-in length"New value: +"Where the fade-in ramp reaches full level, measured from the clip start; the ramp length only when fade_in_start is 0"
    • changedInput schema / properties / fade_in_start / description
      Previous value: -"Fade-in ramp start offset from the clip start"New value: +"Where the fade-in ramp begins, measured from the clip start; negative = before the clip start"
    • changedInput schema / properties / fade_out / description
      Previous value: -"Fade-out length"New value: +"Where the fade-out ramp begins, measured back from the clip end; the ramp length only when fade_out_end is 0"
    • changedInput schema / properties / fade_out_end / description
      Previous value: -"Fade-out ramp end offset from the clip end"New value: +"Where the fade-out ramp reaches silence, measured back from the clip end; negative = past the clip end"
  3. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it explains that values use the selected unit, that 0 clears a fade, how ramp edges are measured, how negative offsets can extend beyond the clip, and that values are clamped. It does not discuss undo grouping, permissions, or return behavior, so it stops short of complete mutation transparency.

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 dense but front-loaded and every sentence earns its place. The technical details about ramp edges, units, clearing, offsets, clamping, and addressing are all necessary for correct invocation of a 12-parameter fade tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complex parameter set and full schema description coverage, the description supplies the behavioral context an agent needs: addressing constraints, unit semantics, clearing behavior, ramp edge arithmetic, crossfade offsets, and clamping. It is complete enough to call the tool correctly without an output schema or annotations.

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?

Schema coverage is already 100%, so the baseline would be 3, but the description adds substantial meaning beyond the schema. It explains the relationship between fade_in and fade_in_start, fade_out and fade_out_end, the unit default, clearing behavior, curve exponent meaning, and a concrete crossfade example.

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 states a specific verb and resource: it sets a clip's fade ramps and fade curve exponents. This is clearly distinct from sibling tools such as clip_gain or clip_speed, and the agent can tell what operation is performed without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied by the operation itself, and the description adds the prerequisite that the address must match exactly one clip. However, it does not explicitly state when to use this tool rather than alternatives like clip_gain, nor does it describe when not to use it.

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