Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_add_generated_audio

Generate and add procedural audio, including a background drone and timed sound events, to a video and save the result to a new file.

Instructions

Add procedurally generated audio to a video.

One-shot convenience function to generate and add audio to video.

Args: input_path: Absolute path to input video. audio_config: Configuration dict with: - drone: {"frequency", "volume"} for background tone - events: List of timed sound events output_path: Absolute path for output video.

Returns: Dict with success status and output_path.

Input Schema

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

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

A3.6/5.0
Behavior3/5

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

With no annotations, the description does add useful behavior: it generates audio procedurally, layers a drone and timed events, writes an output file, and returns success status. However, it omits important operational details such as overwrite behavior, existing-file handling, and any permission or side-effect profile.

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 definition is well structured and front-loaded with the core action, followed by args and returns. There is minor redundancy between the opening sentence and the one-shot convenience sentence, but it is not excessive.

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 four-parameter mutation tool with nested configuration and an output schema, the description covers the essential workflow and required inputs. The output schema handles return values, and the overwrite parameter is covered by the schema, though the description could still say more about mutation side effects.

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 low at 25%, so the description must compensate. It does explain the three required parameters, including absolute input/output paths and the nested audio_config structure with drone frequency/volume and timed events, though it does not fully specify event timing format and leaves overwrite to the schema.

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: add procedurally generated audio to a video. The phrase 'procedurally generated' helps distinguish it from a plain audio-add tool, but it does not explicitly name sibling alternatives such as video_add_audio or audio_synthesize.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Calling it a 'one-shot convenience function to generate and add audio' implies when it is useful, but it gives no explicit when-not conditions or alternatives. The agent must infer that it replaces a separate synthesize-then-add workflow.

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