Skip to main content
Glama
Sign In
ableton12-mcp

ableton12-mcp

by verove-jordan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

compare_audio

Compare two audio files to reveal audible differences in loudness, brightness, punch, width, and dynamics, filtering out imperceptible changes. Verify that a parameter adjustment improved the sound.

Instructions

Diff two audio files (b relative to a) into human-readable deltas — loudness, per-band level, brightness (centroid), punch (low-band crest), width and dynamics, plus a one-line headline. Sub-perceptual changes are suppressed. This is the closed loop's progress meter: capture before/after a parameter move and compare to confirm the change helped.

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": {
      "path_a": "<path_a>",
      "path_b": "<path_b>"
    },
    "name": "compare_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
path_aYes
path_bYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/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. It discloses that it produces human-readable deltas, specifies the exact metrics computed, and notes that sub-perceptual changes are suppressed. It does not mention side effects or error handling, but for a read-only comparison tool, this is adequate.

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

Conciseness5/5

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

The description is two sentences: the first densely lists the output content, the second provides usage context. It is front-loaded with the core function and has zero waste.

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?

The description covers purpose, usage context, parameter relationship, and output characteristics. An output schema exists, so return values are already structured. It lacks file format or path accessibility details, but these are not essential for this tool's core function.

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%, so the description must compensate. It does by explaining that path_b is relative to path_a ('b relative to a'), establishing the directional relationship between the two audio file parameters. This adds meaning beyond the bare titles 'Path A' and 'Path B'.

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 clearly states the tool diffs two audio files into human-readable deltas, listing specific metrics (loudness, per-band level, brightness, punch, width, dynamics) plus a one-line headline. This specific verb+resource+scope distinguishes it from siblings like analyze_audio, which likely analyzes a single file.

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

Usage Guidelines4/5

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

The description gives explicit usage context: 'This is the closed loop's progress meter: capture before/after a parameter move and compare to confirm the change helped.' It clearly indicates when to use the tool, though it does not explicitly name alternatives.

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