Skip to main content
Glama

find_silences

Detect silent or dead-air ranges in a file’s audio with ffmpeg silencedetect. Configure minimum silence length and dBFS threshold to locate cuts.

Instructions

Find silent/dead-air ranges in a file's audio (ffmpeg silencedetect).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_silences"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
minDurationNoMinimum silence length in seconds, default 0.5
thresholdDbNoSilence threshold in dBFS, default -35. Use -30 for noisy rooms, -45 for very clean audio.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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. 'Find' plus the ffmpeg silencedetect reference reasonably conveys a non-destructive analysis pass, but it never states read-only semantics explicitly, whether output is a list of time ranges, or what happens with video-only or unreadable files. The implementation hint adds some value, but the disclosure is thin for a zero-annotation 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?

One short, front-loaded sentence with zero filler and the core resource stated immediately. It is efficient, though its brevity contributes to the specification gaps noted elsewhere.

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?

With three parameters, no annotations, and no output schema, the description should at minimum clarify the meaning of 'path' and the shape of the result. It does neither, so an agent cannot fully predict inputs or outputs from this definition alone.

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 67%: minDuration and thresholdDb are already documented in the schema, including defaults and tuning advice ('-30 for noisy rooms, -45 for very clean audio'). The description adds no parameter meaning of its own and leaves the 'path' parameter ambiguous (filesystem path vs. imported media identifier).

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 verb and resource ('Find silent/dead-air ranges in a file's audio') and even cites the underlying mechanism (ffmpeg silencedetect), so an agent knows precisely what comes back. It does not explicitly position itself against any sibling such as plan_cuts or apply_cuts, which keeps it at 4 rather than 5.

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 prerequisite (e.g. must the file be imported or probed first?), and no mention of how this relates to silence-consuming tools like apply_cuts or plan_cuts. The agent must infer the workflow entirely.

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