Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

glitch_turbulent_displacement

Apply a turbulent displacement glitch effect to video using layered fractal noise, with adjustable amount, scale, speed, and octaves for organic distortion.

Instructions

Apply turbulent displacement glitch effect.

Uses layered sin/cos expressions at different frequencies to approximate fractal Brownian motion noise for organic-looking displacement.

Args: input_path: Absolute path to input video. output_path: Absolute path for output video. amount: Displacement magnitude in pixels. Default 20. scale: Base noise frequency. Default 0.01. speed: Animation speed. Default 1. octaves: Number of noise octaves (1-5). Default 3.

Returns: Dict with success status and output_path.

Input Schema

NameRequiredDescriptionDefault
scaleNo
speedNo
amountNo
octavesNo
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_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.4/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 behavioral burden. It usefully explains the noise model and return shape, but it omits write/overwrite semantics, whether existing outputs are replaced, and safety context around the mutation—important for a video-writing 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 description is front-loaded with the effect and algorithm, then uses structured Args/Returns sections. It is appropriately sized for a tool with several tuning parameters, with little waste.

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 moderately parameterized video effect tool, the description gives enough to invoke it correctly: required input path, output path, and tuning parameters with defaults. The main omissions are overwrite behavior and sibling differentiation, but an output schema exists so return values need not be exhaustively explained.

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 description coverage is very low (14%), so the description must compensate. It documents six of the seven parameters with meaningful units and defaults (pixels, frequency, speed, octave range) and specifies that input/output paths should be absolute, though it does not mention the overwrite parameter.

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 effect: 'Apply turbulent displacement glitch effect', and explains the algorithm briefly. It is clear what the tool does, but it does not distinguish it from the many sibling glitch/transition tools such as glitch_rgb_shift or transition_glitch.

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 the numerous sibling glitch effects or when not to use it. The description only describes the effect and parameters, leaving selection entirely to inference.

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