Skip to main content
Glama
Audionaut MCP Server

Audionaut MCP Server

Set clip gain

clip_gain

Sets the addressed clip's gain - linear by default, dB with db=true - on every destination channel, or one channel. The address (at or region) must match exactly one clip.

Instructions

Sets the addressed clip's gain - linear by default, dB with db=true - on every destination channel, or one channel. The address (at or region) 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>",
      "gain": "<gain>"
    },
    "name": "clip_gain"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoTimeline position of the clip (exclusive with region)
dbNoInterpret gain as decibels
gainYesGain value (linear unless db=true; linear must be >= 0)
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
channelNoOne destination channel (default: all)
projectYesPath to the .audium project package (absolute paths recommended)

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. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral load; it does disclose the key resolution rule (address must match exactly one clip) and the unit-scaling default, which are real behavioral facts. However it says nothing about what happens on a mismatch (error vs no-op), whether gain is absolute or cumulative, or channel-by-channel application semantics.

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 sentences, no filler, and the most surprising detail (default linear scaling) plus the hard precondition are both front-loaded. Nothing is repeated verbatim from the schema.

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 9-parameter mutation tool with full schema coverage and no annotations, the description covers scaling, scope, and addressing adequately. The remaining gap is failure/response behavior, which is left unstated with no output schema to compensate.

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?

Schema coverage is 100%, so the baseline is 3; the description earns more by explaining the interaction the schema only hints at: gain is interpreted linearly unless db=true, and channel silently defaults to all destinations. The 'at or region' exclusivity is also restated in a readable form.

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 ('Sets the addressed clip's gain') and adds precise mechanism detail: linear by default, dB with db=true, applied to all channels or one. It is clear what the tool does, though it does not name which sibling edits (clip_fades, clip_speed) it should be chosen over.

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?

The precondition that the address 'must match exactly one clip' implies when the call is valid, but there is no guidance on when to choose this over sibling edit tools such as clip_fades or clip_speed, and no mention of required project state or ordering.

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