Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

transition_glitch

Apply a glitch transition between two video clips with adjustable duration and intensity to create stylized scene changes.

Instructions

Apply glitch transition between two video clips.

Args: clip1_path: Absolute path to first video clip. clip2_path: Absolute path to second video clip. output_path: Absolute path for output video. duration: Transition duration in seconds (default 0.5). intensity: Glitch intensity 0-1 (default 0.3).

Input Schema

NameRequiredDescriptionDefault
durationNo
intensityNo
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
clip1_pathYes
clip2_pathYes
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.1/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It does not say what happens when output_path already exists (the overwrite requirement), what format the output takes, or whether the operation is expensive/reversible. Writing a new file is a mutation and only the schema's overwrite field hints at the protection behavior.

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 purpose sentence is front-loaded and the args list is terse with no filler. The Args block is slightly rigid but every line earns its place.

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 return values need not be explained, but for a file-writing mutation tool with zero annotations the description should state the overwrite behavior and the default output_path semantics. It covers the core call shape but leaves a meaningful behavioral gap.

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 17%, so the description must compensate and largely does: it explains all six parameters in plain language, including the intensity range 0-1 and duration in seconds. It omits that output_path defaults to null and what that implies (derived path), but the added meaning is substantial.

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 and resource: applying a glitch transition between two video clips. It implicitly distinguishes itself from the many glitch_* effect tools (rgb_shift, scanline_jitter) by being a two-clip transition, but it never names or contrasts with the closest siblings transition_pixelate and transition_morph.

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 tool versus transition_pixelate, transition_morph, or the standalone glitch_* effects. No prerequisites, no constraints on clip compatibility, no guidance on choosing intensity/duration values.

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