Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

image_generate_palette

Generate harmonious color palettes from an image or video frame by extracting dominant colors and applying color-theory harmonies (complementary, analogous, triadic, split-complementary).

Instructions

Generate a color harmony palette from an image or video frame.

Extracts the dominant color and generates harmonious colors based on color theory (complementary, analogous, triadic, split_complementary).

Args: image_path: Absolute path to the image or video file. If video, extracts a representative frame. harmony: Harmony type (complementary, analogous, triadic, split_complementary). n_colors: Number of dominant colors to base palette on (default 5).

Input Schema

NameRequiredDescriptionDefault
harmonyNocomplementary
n_colorsNo
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
image_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 burden, and it omits the most consequential behavior: the presence of an 'overwrite' parameter implies this tool writes media to disk, yet the description never says it produces an output file, where it lands, or what happens on collision. It does disclose the video-frame-extraction behavior, which is real added value, but the write path is left implicit.

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?

One front-loaded summary sentence followed by a compact Args block; every line carries information. Slight structural redundancy between the first sentence and the Args entry for image_path, but no 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?

An output schema exists, so return values need not be spelled out, and the inputs are well covered. What is missing for a tool with four params and zero annotations is the side-effect model: whether files are written, where, and how overwrite interacts with that.

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 25% (only 'overwrite' is documented in the schema), so the description must compensate, and it largely does: it explains image_path accepts video too, enumerates the harmony values that the schema leaves as a bare string with no enum, and gives n_colors' meaning plus default. Only 'overwrite' is unreferenced, but that one is covered by 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?

The description opens with a specific verb and resource ('Generate a color harmony palette from an image or video frame') and then names the underlying mechanism (dominant color extraction plus color-theory harmonies). That is enough to tell it apart from the many video/* siblings, but it never explicitly distinguishes itself from image_extract_colors, which sounds adjacent.

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 statement of when to pick this over image_extract_colors or the still_* / video_* image tools, and no prerequisites or exclusions. The only contextual hint is the passing note that video inputs get a representative frame extracted, which is behavior rather than guidance.

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