Skip to main content
Glama

truncate_silence

Shorten long silent gaps in audio by detecting quiet passages and truncating or compressing them to a set duration.

Instructions

Find and shorten runs of silence in the selected audio.

Args: threshold_db: Silence threshold in dB, -80 to -20. Default: -20.0 minimum_silence: Minimum silence duration to detect, in seconds, >= 0.001. Default: 0.5 truncate_to: Duration to truncate silence down to, in seconds. Default: 0.5 compress_ratio: Percent to compress the remaining silence by, 0-99.9. Default: 50.0 independent_channels: Detect silence independently per channel. Default: False

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
truncate_toNo
threshold_dbNo
compress_ratioNo
minimum_silenceNo
independent_channelsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals the core operation and parameter behavior, including thresholds and durations, but does not state whether the operation is destructive/permanent, whether a selection is required beyond 'selected audio', or what the result/output will look like.

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

Conciseness5/5

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

The description is compact and efficient: one clear purpose sentence followed by a concise parameter list. Every line adds useful information, and there is no filler or repetition.

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

Completeness4/5

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

For a 5-parameter tool with no annotations and no output schema, the description documents the operation and all parameters well. It is slightly incomplete in not addressing usage context relative to sibling tools or clarifying expected output, but it is largely sufficient for correct invocation.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates by documenting all five parameters with units, ranges, and meaning. Each parameter gets a clear explanation: threshold_db, minimum_silence, truncate_to, compress_ratio, and independent_channels.

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 states a specific verb ('Find and shorten') and a clear resource ('runs of silence in the selected audio'). It clearly communicates what the tool does, though it does not explicitly differentiate it from sibling silence-related tools like edit_silence or auto_cleanup_audio.

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 on when to use this tool versus alternatives. The sibling list includes several silence-related operations, but the description provides no exclusions or selection criteria to help an agent choose between them.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xDarkzx/Audacity4-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server