Skip to main content
Glama

audio_analyze

Analyzes audio files to measure loudness (LUFS), true peak, clipping, and silences, and can generate waveform or spectrogram images for review.

Instructions

Audio loudness (LUFS), true peak, clipping, silences; optional waveform/spectrogram image.

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": "<path>"
    },
    "name": "audio_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
imageNo
out_dirNo
silence_dbNo
silence_min_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.6/5.0
Behavior2/5

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

The only annotation is destructiveHint=false, so the description must carry the rest of the behavioral burden. It does not say whether the tool writes anything to disk when out_dir is set, whether it reads the whole file, or how long or costly the analysis takes. The mention of the optional waveform/spectrogram image is useful, but it is not enough for a tool that writes files.

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

Conciseness3/5

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

It is a single compact fragment with no wasted words, and the main measurements come first. However, its telegraphic style omits connecting context that would make it clearer. The brevity comes at the cost of completeness, not just economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a five-parameter tool with no output schema, no meaningful annotations, and no schema descriptions; the description is far too thin for that situation. An agent cannot tell what the tolerance for silence detection is, where files are written, or what the returned metrics look like.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters, so the description has to fill the gap. It explains only that the image parameter accepts waveform or spectrogram and that silence detection exists. It does not explain what out_dir does, what units or default silence_db and silence_min_s use, or what the required path should point to.

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?

The description names a specific resource and a precise set of measurements: loudness in LUFS, true peak, clipping, silences, plus an optional waveform/spectrogram image. That is enough to distinguish it from generic siblings such as media_info or image_compare. It is a noun-phrase fragment without an explicit verb, which slightly weakens it.

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

Usage Guidelines2/5

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

There is no guidance about when to use this tool versus alternatives like media_info. Nothing states prerequisites, supported audio formats, or limits on file size or duration. The only usage signpost is that the image output is optional.

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