Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

glitch_scanline_jitter

Apply a scanline jitter glitch effect by displacing random horizontal pixel rows to create a CRT malfunction look in videos.

Instructions

Apply scanline jitter glitch effect.

Displaces random horizontal rows of pixels for a CRT malfunction look.

Args: input_path: Absolute path to input video. output_path: Absolute path for output video. jitter_amount: Max horizontal displacement in pixels. Default 15. frequency: Fraction of rows affected (0-1). Default 0.3. speed: Animation speed multiplier. Default 5. row_height: Height of each jitter band in pixels. Default 4.

Returns: Dict with success status and output_path.

Input Schema

NameRequiredDescriptionDefault
speedNo
frequencyNo
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYes
row_heightNo
output_pathNo
jitter_amountNo

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.7/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 effect, parameter defaults, and return shape, but it does not explain overwrite protection, whether output_path is required, failure behavior, or processing implications for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core effect and visual result, followed by compact Args and Returns sections. Every sentence adds useful context without filler or repetition.

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?

An output schema exists, so return values do not need extensive explanation. Most parameters are documented and the effect is clear, but the missing overwrite discussion and lack of sibling routing leave minor gaps for a 7-parameter mutation tool.

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 only 14%, so the description must compensate. It explains six of seven parameters with meanings and defaults (jitter_amount, frequency, speed, row_height, input_path, output_path), though it omits overwrite, which is documented in the schema itself.

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 effect (scanline jitter glitch) and explains the visual mechanism: random horizontal row displacement for a CRT malfunction look. It is clear on its own, but does not explicitly distinguish itself from the many sibling glitch effects.

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 description implies usage via 'CRT malfunction look,' giving a creative context, but it provides no explicit when-to-use guidance, exclusions, or alternatives among the numerous glitch siblings (e.g., glitch_screen_tearing, glitch_vhs_tracking).

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