Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

audio_synthesize

Generate WAV audio from mathematical waveforms, with envelopes, reverb, filtering, and fades, eliminating the need for external audio files.

Instructions

Generate audio procedurally using synthesis.

Creates WAV files from scratch using mathematical waveforms. No external audio files needed. Supports envelopes, reverb, filtering, and fade effects.

Args: output_path: Absolute path for the output WAV file. waveform: Waveform type (sine, square, sawtooth, triangle, noise). Default sine. frequency: Base frequency in Hz. Default 440 (A4 note). duration: Duration in seconds. Default 1.0. volume: Amplitude 0-1. Default 0.5. effects: Optional effects dict with keys: - envelope: {"attack", "decay", "sustain", "release"} in seconds - fade_in: Fade in duration in seconds - fade_out: Fade out duration in seconds - reverb: {"room_size", "damping", "wet_level"} - lowpass: Cutoff frequency in Hz

Returns: Dict with success status and output_path.

Input Schema

NameRequiredDescriptionDefault
volumeNo
effectsNo
durationNo
waveformNosine
frequencyNo
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
output_pathNo

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.3/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: it discloses the file-creation side effect and that a success status is returned. However, it never says what happens if output_path already exists or that an overwrite flag is required, nor does it mention validation/error modes for bad paths or frequencies.

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?

Front-loaded purpose sentence followed by an Args/Returns block; every arg line conveys usable defaults or valid values. Slight padding in the repeated 'defaults' phrasing but no wasted structure.

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 file-writing tool with zero annotations, it covers purpose, defaults, the valid waveform set, the effects schema shape, and the return shape (redundant with the output schema but harmless). The one meaningful gap is overwrite/collision behavior, which the schema documents only in passing.

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

Parameters2/5

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

Six of seven parameters gain real meaning here, but one silent behavior matters: the description omits the effects keys it does not cover and never mentions overwrite. Effects values are left underspecified and there is no indication of what happens on an existing path.

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 ('Generate audio procedurally', 'Creates WAV files from scratch using mathematical waveforms') and the mechanism clarifies it is not a file-source tool. It implies the distinction from composing/sequencing siblings ('No external audio files needed') but never names them, so sibling differentiation stays implicit.

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?

The phrase 'No external audio files needed' implies when to use it (synthesizing tones from scratch rather than mixing existing media), but there is no explicit when-to-use/when-not statement and no reference to alternatives like audio_compose, audio_sequence, or audio_preset.

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