Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

effect_scanlines

Apply a CRT-style scanline overlay to video to simulate old monitor lines, with adjustable line height, opacity, and flicker for retro visual effects.

Instructions

Apply CRT-style scanlines overlay.

Simulates old CRT monitor scanline effect with optional flicker.

Args: input_path: Absolute path to input video. output_path: Absolute path for output video. line_height: Pixels per scanline. Default 2. opacity: Line opacity 0-1. Default 0.3. flicker: Brightness variation 0-1. Default 0.1.

Returns: Dict with success status and output_path.

Input Schema

NameRequiredDescriptionDefault
flickerNo
opacityNo
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYes
line_heightNo
output_pathYes

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 behavioral burden. It says the tool applies an effect and returns a success status plus output_path, but does not disclose overwrite behavior, whether the input is modified, or how existing output is handled.

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 and efficiently organized into purpose, Args, and Returns. The Args section repeats some schema defaults, but it remains readable and contextual rather than bloated.

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?

The description covers the effect, most parameters, and the return shape, and an output schema exists. However, for a mutation tool with no annotations, it should more clearly state output overwrite and safety behavior to be fully complete.

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 low at 17%, but the description compensates well by documenting five of six parameters with meaning, ranges, and defaults. The only notable omission is overwrite, which is documented in the schema but not in the description.

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 clearly states a specific verb and resource: applying a CRT-style scanlines overlay with optional flicker. It is distinguishable from most siblings, but it does not explicitly differentiate itself from the closely related glitch_scanline_jitter tool.

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?

The description implies the visual use case but gives no explicit guidance on when to use this effect versus alternatives such as glitch_scanline_jitter, effect_vignette, or other glitch/effect tools. It also omits prerequisites or exclusions.

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