Skip to main content
Glama

Measure File

audacity_measure_file
Read-onlyIdempotent

Measure WAV or other audio files without opening Audacity, reporting peak, RMS, DC offset, crest factor, and optional LUFS/true peak against target ranges.

Instructions

Measure an exported/source audio file without touching Audacity. Native PCM/float WAV peak/RMS/DC/crest and advisory defects need no dependencies; ffmpeg on PATH adds EBU R128 LUFS/LRA/true peak and decodes other containers. Unavailable targets report unknown. With targets, returns {measurement,targetCheck}; otherwise returns the measurement directly.

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": "<file>"
    },
    "name": "audacity_measure_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
backendNoauto
targetsNo
dualMonoNo
timeoutMsNo

Output Schema

NameRequiredDescriptionDefault
rmsNo
fileNo
peakNo
notesNo
scopeNo
framesNo
backendNo
crestDbNo
rmsDbfsNo
channelsNo
dcOffsetNo
dualMonoNo
durationNo
peakDbfsNo
perChannelNo
sampleRateNo
measurementNo
silenceGapsNo
targetCheckNo
unavailableNo
truePeakDbtpNo
clippedSamplesNo
integratedLufsNo
discontinuitiesNo
loudnessRangeLuNo
silenceGapCountNo
quietRmsDbfsEstimateNo
dynamicRangeDbEstimateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuine operational detail: native WAV path needs no dependencies, ffmpeg unlocks EBU R128/true peak and other containers, and unavailable targets are reported as 'unknown' rather than failing. It does not discuss error modes for unreadable files or how long-running decodes behave against timeoutMs.

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?

Tight, front-loaded prose with no filler; the dependency sentence and the conditional return-shape sentence both earn their place. It is dense with jargon but not padded.

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?

Given a dedicated output schema, the description covers the parts that schema can't: environment dependencies, decode fallback, and the unknown-target behavior. Gaps remain around the unexplained parameters (dualMono, timeoutMs, backend enum) and file-error handling, which keeps it below full marks.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with 5 parameters including a nested targets object, so the description carries the burden. It explains what targets does (produces {measurement,targetCheck}) and implies backend behavior, but never explains the backend enum values, dualMono, timeoutMs, or the individual target keys (rmsDbfs, integratedLufs, truePeakDbtp, etc.).

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?

States a specific verb and resource (measure an audio *file*) plus the scope that separates it from the in-Audacity sibling: 'without touching Audacity'. An agent can tell this apart from audacity_measure and audacity_probe_file without opening a schema.

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 context is implied rather than stated: it is for an exported/source file on disk, and ffmpeg-on-PATH is needed for non-WAV containers. No alternative tool is named and no when-not-to-use case is given, so routing remains partly inferential.

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