Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

glitch_cmyk_split

Apply a CMYK split glitch effect to videos by shifting RGB channels at 90-degree intervals, simulating four-plate offset print registration errors.

Instructions

Apply CMYK split glitch effect.

Shifts RGB channels at 90-degree intervals to simulate four-plate offset print registration errors.

Args: input_path: Absolute path to input video. output_path: Absolute path for output video. amount: Shift distance in pixels. Default 8. angle: Base angle in degrees. Default 0. noise: Per-frame noise amplitude (0-1). Default 0.

Returns: Dict with success status and output_path.

Input Schema

NameRequiredDescriptionDefault
angleNo
noiseNo
amountNo
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

A3.6/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 visual transformation and mentions the return payload, but it omits operational behavior such as overwrite handling, whether existing output is replaced, and file-safety expectations, even though those matter for a processing 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 purpose and effect mechanics, then moves into parameters and return value in a predictable structure. It is efficient, though it repeats schema defaults and includes a return sentence that is redundant given the output schema.

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 single-effect video tool with an output schema and a schema-described overwrite flag, the definition is largely complete enough to invoke correctly. The main missing context is sibling differentiation and explicit overwrite/file-safety guidance, but the core effect and key parameter meanings are covered.

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 17%, so the description must compensate, and it does for five of six parameters: input/output paths, amount in pixels, angle in degrees, and noise on a 0-1 scale. It omits the overwrite parameter, but the schema itself provides a description for overwrite, limiting the gap.

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: it applies a CMYK split glitch by shifting RGB channels at 90-degree intervals to simulate four-plate registration errors. That is clearer than a generic glitch tool, but it does not explicitly differentiate this from close siblings 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 Guidelines3/5

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

Usage is implied by the effect description: an agent can infer it should use this when it wants a CMYK split / print-registration glitch look. However, the description gives no explicit when-to-use guidance, no exclusions, and no recommendation among the many glitch and transition siblings.

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