Skip to main content
Glama
Podcast MCP
by calebn

set_clip_gain_tool

Sets a single clip's gain in dB from -60 to +12 before track processing and fader, so you can adjust clip level without altering the track chain. Out-of-range values are refused.

Instructions

Set the level of a single clip in dB (0 = unity, range -60 to +12).

Clip gain applies before the track chain, staging gain, and fader. A value outside the range is refused. Changing it makes the track's stem stale.

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": {
      "clip_id": "<clip_id>",
      "gain_db": "<gain_db>"
    },
    "name": "set_clip_gain_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_idYes
gain_dbYes
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A3.7/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 burden and does well: it discloses that gain applies before the track chain, staging gain, and fader, that out-of-range values are refused rather than clamped, and that the change invalidates the track's stem. It stops short of saying whether the change is undoable or what permissions/context are required, which are meaningful gaps for a mutation tool.

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

Conciseness4/5

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

Four short sentences with the operative constraint (range, unity) front-loaded, followed by signal-chain context and the side effect. Dense and readable, though the 'refused' sentence is somewhat redundant with the stated range.

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, so return values need not be described. For a no-annotation mutation tool the description covers the important behavior (range enforcement, chain position, stale stem), leaving only minor gaps around the optional project_path and undo semantics.

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 compensate, and it only partly does: it fully explains gain_db (units, unity point, valid range, out-of-range behavior) but says nothing about clip_id format/scope or what project_path is for or when it should be supplied.

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?

The description states a specific verb and resource ('Set the level of a single clip'), scoped to one clip and quantified in dB. The word 'single' implicitly separates it from the plural sibling set_clips_gain_tool, but that sibling is never named, so the differentiation is left for the agent to infer.

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 'single clip' scope, but there is no explicit when-to-use guidance, no statement about when to prefer set_clips_gain_tool instead, and no mention of preconditions such as needing an active project or an existing clip.

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

Deploy Server

Other Tools