Skip to main content
Glama

analyze_mix

Analyze a WAV/AIFF mix for loudness, true peak, spectrum balance, resonances and stereo issues, returning ranked findings with fixes against streaming, club, broadcast or podcast targets.

Instructions

Mastering-engineer report on a WAV/AIFF mix: loudness per ITU-R BS.1770 / EBU R128 (integrated, short-term and momentary max, loudness range), true peak (4x oversampled), PLR, crest factor, long-term 1/3-octave spectrum with tilt and per-region deviation from a balanced -4.5 dB/oct reference (mud, harshness, sibilance, air, sub), narrow resonances (with note names), stereo correlation and width overall and per band (low-end mono), DC. Returns findings ranked problème / attention / ok with concrete fixes against the delivery target, plus a spectrogram image (log frequency, with the short-term loudness curve) to look at.

Parameters:

  • file_path: Absolute path of the audio file

  • target: "streaming" (default, -14 LUFS), "club", "classical", "broadcast" (EBU -23 LUFS) or "podcast"

  • spectrogram: Also return the spectrogram image (default True)

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": {
      "file_path": "<file_path>"
    },
    "name": "analyze_mix"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNostreaming
file_pathYes
spectrogramNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses the reference curve (-4.5 dB/oct), true-peak oversampling (4x), that findings are ranked problème/attention/ok with concrete fixes, and that a spectrogram image is returned with a log-frequency axis. It does not state read-only safety, runtime cost, or supported duration, which would round out a heavy analysis 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?

It is front-loaded with the deliverable ('Mastering-engineer report') and then packs the metric list tightly, with the return behavior at the end where it belongs. The middle sentence is a long parenthetical pile-up that is dense but nearly every clause adds a distinct measurement, so little is wasted.

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?

There is no output schema, so the description must explain returns itself, and it does: ranked findings with fixes plus an optional spectrogram image with a loudness curve overlay. Gaps remain around error conditions (unsupported format, short/empty file) and whether the report is text-only or also structured, but the coverage is strong for a 3-parameter analysis tool.

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 0% and the schema has no enums, so the prose is doing real work: it documents file_path as an absolute path, spells out all five target values with their LUFS references (-14 streaming, EBU -23 broadcast), and explains that spectrogram toggles the returned image. The non-streaming targets ('club', 'classical', 'podcast') are named but their numeric references are not given, and the target string is not listed as a closed enum.

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 opens with a specific verb and resource ('Mastering-engineer report on a WAV/AIFF mix') and then enumerates exactly what is measured: BS.1770/R128 loudness, true peak, PLR, crest factor, 1/3-octave spectrum with tilt, resonances, stereo correlation, DC. That is far more specific than the sibling names suggest for a generic analyzer, so an agent can distinguish this mastering/QC report from a plain audio analysis.

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 rather than stated: the rankings and 'concrete fixes against the delivery target' tell the agent this is for mix QC before delivery, and the target parameter hints at delivery-context selection. However, there is no explicit when-to-use/when-not guidance and no mention of how it relates to analyze_audio_file or analyze_clip_music. Meaningful but inferential.

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