Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_audio_waveform

Extract audio waveform peaks and silence regions from video or audio files to analyze audio dynamics and detect quiet segments for editing decisions.

Instructions

Extract audio waveform data (peaks and silence regions).

Args: input_path: Absolute path to the input video/audio file. bins: Number of time segments to analyze (default 50).

Input Schema

NameRequiredDescriptionDefault
binsNo
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.4
    • addedInput schema / properties / overwrite
      Added value: +{
+  "default": false,
+  "description": "Explicitly allow replacing existing media. Existing non-media files are protected.",
+  "title": "Overwrite",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.16.0
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv1.5.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It never says whether this is read-only or writes an artifact, despite the presence of an 'overwrite' parameter that strongly implies file output — a meaningful gap for a no-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?

The core purpose sentence is front-loaded and the parameter notes are terse. The 'Args:' block is boilerplate but does not bloat the text.

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?

An output schema exists, so the shape of the peaks/silence result need not be restated. However, for a no-annotation tool with an overwrite flag, the description should clarify whether files are written and what overwrite protects against.

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

Parameters4/5

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

Schema coverage is only 33%, but the description compensates by documenting the two undocumented parameters: input_path as an absolute path to a video/audio file, and bins as the number of time segments (default 50). Only 'overwrite' is left to the schema, which handles it well.

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 and resource ('Extract audio waveform data') and narrows the output to 'peaks and silence regions', which distinguishes it from audio-file extraction siblings like video_extract_audio. It does not explicitly name a sibling to disambiguate against, so it stops short of a 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 statement of when to use this versus video_extract_audio, video_audio_spatial, video_normalize_audio, or video_analyze. The only context is implicit in the tool name, leaving the agent to infer that this is an analysis step rather than a media-producing one.

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

Deploy Server

Other Tools