Skip to main content
Glama

convert_audio

Convert audio files between formats such as MP3, WAV, FLAC, and OGG, and apply trims, fades, normalization, volume changes, bitrate, sample rate, or channel settings.

Instructions

Convert audio files. Input: mp3, wav, flac, aac, ogg, m4a, aiff, opus, wma, ac3, dts, amr, ra, wv, ape, tta, mka. Output: mp3, wav, flac, aac, ogg, m4a, aiff, opus, wma, ac3, amr, wv, mka. Supports: trim, fade in/out, normalize, volume adjust.

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": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "convert_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
fadeInNoFade in duration in seconds (optional)
volumeNoVolume adjustment in dB e.g. 3 or -6 (optional)
bitrateNoOutput bitrate e.g. '320k', '192k' (optional)
fadeOutNoFade out duration in seconds (optional)
channelsNo1=mono, 2=stereo (optional)
durationNoTrim duration e.g. '00:02:00' (optional)
inputPathYesAbsolute path to input audio file
normalizeNoApply loudnorm normalization (optional)
startTimeNoTrim start e.g. '00:01:30' (optional)
outputPathYesAbsolute path for output file (include extension)
sampleRateNoSample rate in Hz e.g. 44100, 48000 (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it does disclose the genuine support surface (format matrix plus trim, fade, normalize, volume). It says nothing about what happens on write, e.g. whether outputPath is overwritten, whether the parent directory must exist, or how failures surface – real gaps for a file-writing tool.

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?

Front-loaded with the core verb and resource, followed by the format matrix and operation list in two compact sentences. The long enumerations are informative rather than wasteful, though the asymmetry between the 17-item input list and 14-item output list could be tightened.

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

Completeness3/5

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

With 11 parameters, no output schema, and no annotations, the description covers capability but not outcome: the return value, whether the tool reports duration/format of the produced file, and error behavior are all unaddressed. Adequate to start a call, insufficient to predict what the call produces.

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 coverage is 100%, so all 11 parameters are already fully documented with types and examples, which establishes the baseline of 3. The description adds only the implied rule that the output format is inferred from the outputPath extension, which the schema only hints at with "include extension".

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?

"Convert audio files" is a clear verb+resource, and the input/output format lists pin down the scope of the conversion domain. It does not differentiate from plausible siblings such as convert_music, convert_video, or batch_convert, so an agent cannot tell from the text alone which 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 Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given; the format lists are capability data, not routing advice. There is no mention of when to prefer batch_convert for multiple files or convert_music for music-specific needs, leaving selection entirely to inference.

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