Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_chroma_key

Remove a solid color background from video using chroma key. Make green screen colors transparent with adjustable similarity and blend for compositing.

Instructions

Remove a solid color background (green screen / chroma key).

Args: input_path: Absolute path to the input video. color: Color to make transparent in hex format (default green: 0x00FF00). similarity: How similar colors need to be to be keyed out (0.0-1.0, default 0.01). blend: How much to blend the keyed color (default 0.0). output_path: Where to save the output. Auto-generated if omitted.

Input Schema

NameRequiredDescriptionDefault
blendNo
colorNo0x00FF00
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
input_pathYes
similarityNo
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.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It says the tool removes a background and can auto-generate output_path, but it does not disclose overwrite behavior, file protection, whether the input is modified, processing characteristics, or other operational details.

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?

The description is front-loaded with the purpose and then uses a compact Args list to clarify parameters. It is appropriately sized for a tool with low schema description coverage and contains no obvious filler.

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 definition is adequate for invoking the tool, especially because an output schema exists and most parameters are explained. However, with no annotations and no usage guidance against alternatives, it leaves gaps around when to choose chroma key versus luma key or background removal, and it does not mention overwrite behavior.

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%, so the description usefully documents input_path, color format/default, similarity range/default, blend default, and output_path auto-generation. It omits the overwrite parameter, but that parameter is described in the schema and the description compensates well for most other undocumented parameters.

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: removing a solid-color background via chroma key. It is understandable without opening the schema, but it does not explicitly differentiate this from sibling tools such as video_luma_key or hyperframes_remove_background.

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 explains parameters but gives no guidance on when to use this tool versus alternatives like video_luma_key, hyperframes_remove_background, or other masking tools. It implies green-screen use but does not state when-not to use it or what prerequisites exist.

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