Skip to main content
Glama
ffmpeg-mcp

ffmpeg-mcp

by yambal

adjust_volume

Adjust an audio file's volume by percentage or decibels, writing the result to a specified output path.

Instructions

Adjust the volume of an audio file

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": {
      "input_path": "<input_path>",
      "output_path": "<output_path>",
      "volume": "<volume>"
    },
    "name": "adjust_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
volumeYesVolume adjustment (e.g., '0.5' for 50%, '2.0' for 200%, '10dB' for +10dB, '-5dB' for -5dB)
input_pathYesPath to the input audio file
output_pathYesPath for the output audio file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it doesn't state whether the input file is left untouched or that a new file is written to output_path, nor which audio formats are supported. The only behavioral hint, the presence of output_path, comes from the schema, not the description.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the brevity borders on under-specification rather than tightness.

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?

For a three-parameter, fully-described schema with no output schema, the description is technically sufficient to call the tool. It leaves key behavioral questions unanswered (non-destructive write, supported formats) that matter for an audio mutation tool with no annotations.

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 100%, and the volume parameter already has rich examples ('0.5', '2.0', '10dB', '-5dB') in the schema. The description adds no meaning beyond that, so the baseline 3 applies.

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 ('Adjust') and resource ('volume of an audio file'), which is unambiguous about the operation. It stops short of differentiating from the audio siblings (convert/trim/merge), but the verb-resource pair is distinct enough that confusion is unlikely.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as convert_audio or trim_audio. Usage is only implied by the one-line purpose statement.

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