Skip to main content
Glama

Create colour wheels (lift/gamma/gain)

create_color_wheels

Builds a classic three-wheel color grade chain with lift, gamma, and gain controls plus offset and saturation. Accepts source TOP or generates a test gradient for standalone preview.

Instructions

Classic colour-grading wheels — three tinted Level TOPs run in series for shadows (lift, gamma-biased), midtones (gamma) and highlights (gain, brightness-biased), then a master Level TOP for global offset (blacklevel), then an HSV Adjust TOP for saturation. Each wheel is an [r,g,b] multiplier in 0..2 (1,1,1 = neutral). Builds a new baseCOMP under parent_path holding the chain; with source_path the upstream TOP is pulled in via a Select TOP, without one a Ramp TOP test gradient is graded so the chain previews standalone. Exposes per-channel LiftR/G/B, GammaR/G/B, GainR/G/B float knobs plus Offset and Saturation (live-bound to the underlying Level/HSV pars). Output is a Null TOP. Use create_color_grade for a simpler single-Level + HSV chain, or apply_post_processing to chain several distinct effects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_pathNoAbsolute path of the source TOP to grade. Pulled in via a Select TOP (TD wires don't cross containers). If omitted, a Ramp TOP test gradient is graded so the chain still builds and previews without any external source.
liftNoShadow tint (lift wheel) as [r,g,b] in 0..2. Multiplies R/G/B on a Level TOP whose `gamma1` is biased high (~1.4) so the multiply lands in the darker tonal range. [1,1,1] = neutral.
gammaNoMidtone tint (gamma wheel) as [r,g,b] in 0..2. Multiplies R/G/B on a mid-biased Level TOP. [1,1,1] = neutral.
gainNoHighlight tint (gain wheel) as [r,g,b] in 0..2. Multiplies R/G/B on a Level TOP biased into highlights via `brightness1`. [1,1,1] = neutral.
offsetNoGlobal black-level offset (-1..1). Positive lifts the black point (faded/filmic look); negative crushes. Drives the master Level TOP's `blacklevel`.
saturationNoMaster saturation multiplier (1 = unchanged, 0 = greyscale). Drives the trailing HSV Adjust TOP's `saturationmult`.
expose_controlsNoWhen true (default), expose live per-channel float knobs LiftR/G/B, GammaR/G/B, GainR/G/B (0..2, 1 = neutral) plus Offset and Saturation. Three floats per wheel — instead of a single RGB swatch — because the shared control-panel builder cannot bind an `rgb` control to a parameter, so the swatch would be display-only.
base_nameNoOptional base name for the container (defaults to 'color_wheels'). Final container path is `<parent_path>/<base_name>` with TD's auto-suffix.
parent_pathNoParent network where the colour-wheels container is created (default '/project1')./project1
Behavior5/5

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

The description discloses the internal chain, value ranges, default behaviors, and knob exposure rationale, adding detail beyond the annotations which only indicate non-readonly and non-destructive.

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 concise at ~150 words, front-loaded with the core purpose, then details and alternatives. No wasted sentences.

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?

Despite no output schema, the description covers output (Null TOP), parameter effects, internal chain, and usage scenarios, fully equipping an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Every parameter description adds mechanistic detail (e.g., lift biased gamma1, expose_controls rationale) beyond the schema's type/min/max, enhancing understanding.

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 classic color-grading wheels chain with three Level TOPs and HSV Adjust. It differentiates from siblings like create_color_grade and apply_post_processing.

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

Usage Guidelines5/5

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

It explains when to use (classic color grading), what happens with optional source, and explicitly names alternatives for simpler or chained effects.

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