Skip to main content
Glama

mix_audio

Combine up to eight local audio tracks with adjustable gain and delay, then apply an output limiter via FFmpeg.

Instructions

Mix real local tracks with bounded gain/delay and output limiter via FFmpeg.

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": {
      "tracks": "<tracks>",
      "output": "<output>",
      "duration": "<duration>"
    },
    "name": "mix_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputYes
tracksYes
durationYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare the operation is non-read-only, non-destructive, non-idempotent, and closed-world, and the description is consistent with that. It adds real value by disclosing the FFmpeg backend and an output limiter, but says nothing about whether the output file is overwritten, what happens on FFmpeg failure, or resource cost.

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?

A single dense sentence with no filler, front-loading the core action and constraints. It is arguably too terse rather than bloated, so conciseness itself is a strength.

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

Completeness2/5

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

The output schema covers return values, but this is a file-producing mutation tool with three required parameters at 0% schema documentation. Critical details are missing: what duration controls, whether output overwrites an existing file, and the actual gain/delay bounds, leaving the agent to guess.

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

Parameters2/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 carry parameter meaning, and it only partially does: 'bounded gain/delay' hints at the gain and delayMilliseconds ranges but never states the limits, the 8-track cap, or that duration is a mix length in seconds. The output parameter's meaning is entirely undocumented.

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 (mix) and resource (real local tracks) plus behavioral constraints (bounded gain/delay, output limiter, FFmpeg backend). An agent can tell this is a local audio-mixing/rendering step, distinct from import or level-inspection siblings, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as import_audio or inspect_audio_levels. 'Real local tracks' weakly implies files must exist locally, but nothing tells the agent when this tool is the right choice versus inspecting or syncing audio first.

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