Concatenate two to 20 local audio files into a single WAV, OGG, MP3, or FLAC output using FFmpeg's audio concat filter.
Concatenate local audio files through FFmpeg's audio concat filter.
| Name | Required | Description | Default |
|---|---|---|---|
| format | Yes | ||
| filename | Yes | ||
| overwrite | No | ||
| input_paths | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full burden. It hints at local filesystem access but omits whether files are re-encoded, where the output is written, whether existing files are overwritten, and what happens on format mismatch between inputs — significant 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler or redundancy. It is lean, though the brevity comes at the cost of necessary detail rather than being a model of efficient completeness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 4-parameter mutation tool with no annotations and no output schema, the definition is under-specified: ordering of inputs, output destination, and overwrite semantics are all unstated. It orients the agent to what the tool is but not enough to invoke it confidently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% across 4 parameters, so the description must compensate and does not. It says nothing about filename, format enum choices, the overwrite flag, or the 2–20 input constraint, adding no meaning beyond the bare schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb (concatenate) plus resource (local audio files) and names the implementation (FFmpeg concat filter). It distinguishes itself reasonably from siblings like split_audio, trim_audio, and convert_audio, though it doesn't explicitly contrast with them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance and no named alternatives. It never says when to pick merge_audio over split_audio, create_audio_loop, or create_composition_plan, nor any prerequisites such as matching sample rates or formats across inputs.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.