Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ABLETON_AUTO_MIX_STYLES_DIRNoCustom styles directory (optional). Overrides the default styles package.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_stylesA

List all available mixing styles with their targets.

Read-only. Call this first to discover style names; pass one to get_style, auto_mix or preview_mix.

get_styleA

Get the full profile for a style, including spectral curve, track balance, compression and FX recommendations.

Read-only. Call list_styles first to see the available names, then pass one here to fetch its detailed profile.

get_ableton_statusA

Check connection to Ableton Live and return basic project info.

analyze_audioA

Analyze a rendered WAV file into mix metrics: loudness (LUFS/LRA), RMS, peak, spectral band energy and stereo width.

Read-only. Use on a single bounced render. For a whole folder of renders, use analyze_render_dir instead.

analyze_render_dirA

Analyze every WAV in a directory of rendered tracks. Point this at the folder where you bounced the Ableton tracks (one WAV per track).

Read-only, batch variant of analyze_audio. Run this before auto_mix or preview_mix so the renders are measured against the style profile.

auto_mixA

Auto-mix rendered tracks toward a musical style.

Args: style: style name (see list_styles) render_dir: folder containing one WAV per track (bounced from Ableton) dry_run: True returns recommendations without touching Ableton; False applies the volume/pan corrections to the Live set. pattern: glob for audio files inside render_dir

Returns: Per-track corrections (levels, pan, EQ band deltas) and master notes.

Call with dry_run=True first to review the recommendations; only use dry_run=False to apply them to the Live set. Requires Ableton Live + AbletonOSC for dry_run=False; the dry run works offline.

preview_mixA

Apply the style corrections to the rendered WAVs and bounce a stereo preview mix you can listen to WITHOUT Ableton: volumes + pans are applied to the audio directly, tracks are summed, and the result is normalized to the style's target loudness. Returns the path to the preview WAV.

Args: style: style name (see list_styles) render_dir: folder containing one WAV per track pattern: glob for audio files inside render_dir output_path: where to write the preview (default: /preview_.wav) max_duration: cap preview length in seconds. When renders have mismatched lengths (loops vs full arrangement), pass the loop length so the preview stays a tight section. If None, all tracks are trimmed to the shortest render. manual_gain: extra per-file volume in dB, keyed by the render file name without extension, e.g. {"snt2": -4.0}. sidechain_db: duck all non-snare tracks by this many dB when a snare hits, e.g. -4.0 for a light pump. None disables it.

Works fully offline (no Ableton needed) as long as the render WAVs exist. Use this to listen to the mix before applying anything in Live; for recommendations only, use auto_mix with dry_run=True.

suggest_styleA

Analyze the rendered tracks and suggest which style profile fits best.

Read-only. Use this before auto_mix when you are unsure which style to pick; the returned profile name can then be passed to auto_mix or preview_mix.

analyze_conflictsA

Analyze the rendered tracks and report which pairs are fighting for the same frequency band (e.g. bass vs sub, snare vs bass). Each conflict comes with an actionable suggestion (high-pass, EQ cut, ducking).

Read-only diagnostic. Run before auto_mix to plan EQ/ducking decisions.

release_checkA

Run the mix through a label-style quality gate.

If output_path is not given, it re-renders the preview for the requested style (or reuses the existing preview file) and measures it against top-label targets: LUFS, LRA, true peak, RMS and spectral tilt. Returns a ready/needs_work verdict with per-metric results.

Read-only for your audio files; it may write a preview WAV when output_path is omitted. Run this last, after preview_mix, to decide whether the mix is release-ready.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have clearly distinct purposes: querying status, listing/fetching styles, analyzing audio in two forms, auto-mixing, previewing, suggesting styles, analyzing conflicts, and release checking. The two analyze tools (analyze_audio vs analyze_render_dir) could be confused at first glance, but descriptions clearly differentiate single-file vs directory batch, so boundary is well-defined.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: get_ableton_status, list_styles, get_style, analyze_audio, analyze_render_dir, auto_mix, preview_mix, suggest_style, analyze_conflicts, release_check. There are no deviations in style or mixed conventions.

Tool Count5/5

Ten tools is firmly in the well-scoped range for an audio mixing server. Each tool maps to a distinct workflow step (discover, analyze, suggest, preview, apply, verify), and none feels redundant or placeholder.

Completeness4/5

The surface covers the full workflow: style discovery, audio analysis, auto-mixing, offline preview, style suggestion, conflict diagnostics, and a final release gate. Minor gaps include the absence of a tool to apply or revert individual mix corrections outside of auto_mix, and no explicit way to manage/edit style profiles—but these are secondary to the core mixing workflow.

Maintenance

ActivityMaintained
ResponsivenessNo issues