Skip to main content
Glama

Create colour palette / gradient

create_palette

Generate a colour palette and gradient with colour-theory rules or from an image source. Provides swatches and a ramp for use in colour grading or moodboard creation.

Instructions

Generate a reusable colour palette + gradient other tools can bind to. In 'harmony' mode it computes N swatches from a base hue and a colour-theory rule (complementary / analogous / triad / tetrad / monochrome); in 'from_source' mode it samples dominant colours from a source TOP. It builds a Ramp TOP gradient (key colours from a docked Table DAT) plus a Constant CHOP exposing each swatch as swatch{i}r/g/b channels — feed those into create_color_grade, generate_from_moodboard or bind_to_channel. Live BaseHue / Saturation / Value / Rule / Count controls are exposed on the parent. Builds standalone (a harmony palette needs no source).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoHow swatches are derived: 'harmony' computes them from a base hue + a colour-theory rule (pure maths); 'from_source' samples dominant colours from a source TOP.harmony
base_hueNo(harmony) Base hue on the colour wheel, 0..1 (0 = red, 0.333 = green, 0.666 = blue).
saturationNo(harmony) Base saturation 0..1 (0 = grey, 1 = vivid).
valueNo(harmony) Base value / brightness 0..1.
ruleNo(harmony) Colour-theory spread: complementary (base + opposite), analogous (neighbours), triad (3 evenly spaced), tetrad (4 evenly spaced), monochrome (one hue, varied brightness).triad
countNoNumber of swatches to produce (1..13; capped because the swatch Constant CHOP holds 40 channels = 13 RGB swatches).
analogous_spreadNo(harmony, analogous rule) Hue step between neighbours, 0..0.5 (0.083 ≈ 30°).
sourceNo(from_source) Absolute path of a TOP to sample dominant colours from. It is down-res'd to a tiny image and its pixels are read back; if missing/unreadable the palette falls back to a neutral greyscale ramp.
parent_pathNoCOMP to build the Ramp TOP + swatch CHOP inside./project1
nameNoBase name for the created nodes.palette
expose_controlsNoAdd BaseHue / Saturation / Value / Rule / Count custom parameters to parent_path.
Behavior5/5

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

Annotations already indicate mutability (readOnlyHint=false) and non-destructiveness. The description adds crucial behavioral context: node creation (Ramp TOP, Constant CHOP, Table DAT), exposure of live controls, fallback to greyscale ramp in from_source mode if source is missing, and count cap due to channel limits. No contradiction with annotations.

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 four sentences, front-loaded with the core purpose, and each sentence adds distinct value (mode explanation, outputs, usage examples, behavioral notes). No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description sufficiently explains what is built (Ramp TOP with gradient, Constant CHOP with swatch channels) and how to feed into other tools. It covers both modes, fallback behavior, and control exposure. Complete for the tool's complexity.

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 coverage is 100%, but the description adds value by explaining mode-specific parameter relevance, the role of expose_controls, and the meaning of analogous_spread. It avoids redundancy and provides practical context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a reusable colour palette/gradient and distinguishes two modes ('harmony' and 'from_source'). It identifies the resources built (Ramp TOP, Constant CHOP) and how outputs are used with sibling tools (create_color_grade, generate_from_moodboard, bind_to_channel). This differentiates it effectively from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description provides clear context for each mode: harmony for no source, from_source for sampling from a TOP. It suggests downstream tools but does not explicitly state when not to use this tool or compare with direct alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server