LiveSession MCP

Overview Schema Source Related Servers Discussions Admin

gain_stage

Destructive

Sets track fader levels so each peaks at a target dBFS by playing the song and monitoring peak meters, creating a clean starting balance before mixing.

Instructions

Play the song and watch every track's peak meter for a few seconds, then set faders so each track peaks around target_peak_db (default -6 dBFS) — a clean starting balance before mixing. Tracks that stay silent are left alone. apply=False only reports.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gain_stage"
  }
}

Input Schema

Name	Required	Description	Default
`apply`	No
`seconds`	No
`start_beat`	No
`target_peak_db`	No
`include_returns`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Nov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing the major side effect the hints don't capture: it starts playback for a measured window and leaves silent tracks untouched. The apply=False reporting mode is a useful dry-run signal for a destructiveHint=true tool. It stops short of saying whether prior fader values are recoverable or undoable.

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?

Front-loaded with the core action, then the target and the silent-track caveat, then the dry-run note. Slightly dense in one long sentence but no filler.

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 mutating multi-step tool, the description covers the operational sequence, scope (every track vs silent tracks), and a safe reporting mode; the presence of an output schema relieves it of explaining return values. Only the unaddressed start_beat and include_returns keep it from full completeness.

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?

With 0% schema description coverage the schema explains nothing, and the description fills in apply (dry-run), target_peak_db (with its -6 dBFS default) and roughly 'seconds'. start_beat and include_returns are never mentioned, so two of five parameters remain opaque.

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 concrete compound action: play the song, meter each track, and set faders to hit target_peak_db, framed as 'a clean starting balance before mixing.' That distinguishes it from low-level siblings like get_meters and set_mixer, though it never names them.

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 context is implied ('a clean starting balance before mixing') and the dry-run path is called out ('apply=False only reports'). There is no explicit when-not guidance or pointer to alternative tools for manual meter reading or fader adjustment.

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

Deploy Server