Skip to main content
Glama

analyze_audio_file

Measure WAV or AIFF peak/RMS levels, clipping, loudness, silence, stereo correlation, and spectral balance to verify a mix or recorded take.

Instructions

Measure a WAV or AIFF file: peak and RMS levels (dBFS), clipping, crest factor, loudness over time (one value per segment), leading/trailing silence, stereo correlation and a coarse spectral balance (low < 250 Hz, mid, high > 4 kHz), with warnings. Use it to check a mix or a recorded take.

Parameters:

  • file_path: Absolute path of the audio file

  • segment_seconds: Length of each loudness segment (default 1 s)

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_audio_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes
segment_secondsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the entire behavioral burden. It does useful work by constraining accepted formats ('WAV or AIFF') and disclosing that per-segment loudness values and warnings are returned, which implies a measurement-only, non-mutating operation. It never explicitly states that the tool is read-only, does not describe error behavior for missing/unsupported files or mono files, and gives no sense of cost on long files.

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?

The output is front-loaded with the verb and the accepted formats, then the metric list, then the invocation hint, then a compact parameter block. Every sentence carries content; the metric enumeration is dense but earns its place by telling the agent what it will get back. Slight cost in readability from packing everything into one long sentence.

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?

An output schema exists, so return-value structure need not be spelled out, and the description correctly stops at naming which measurements are produced plus the presence of warnings. For a two-parameter, format-constrained analysis tool this is nearly complete; only failure modes and the absence of explicit read-only framing keep it from being fully self-sufficient.

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 description coverage is 0%, so the description must supply all parameter meaning, and it does cover both parameters: file_path as an 'Absolute path of the audio file' and segment_seconds as segment length with a default of 1 s. This is the key information the bare schema lacks, notably that file_path is a local absolute path rather than an ID or URI. Minor gap: no bounds or guidance on useful segment_seconds values.

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 ('Measure') and resource (WAV/AIFF audio file) and enumerates exactly which metrics are produced: peak/RMS dBFS, clipping, crest factor, per-segment loudness, silence, stereo correlation, spectral balance, plus warnings. That is far more than a restatement of the name. It does not, however, distinguish itself from analysis-type siblings such as analyze_mix or analyze_clip_music, so an agent cannot tell solely from this text which analyzer to pick.

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?

'Use it to check a mix or a recorded take' gives an implied scenario for invocation, which is real but thin. There is no statement of when NOT to use it, no prerequisite checks (file must already exist, must be WAV/AIFF rather than compressed), and no named alternative tool for mix-level or clip-level analysis.

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