Skip to main content
Glama
Sign In
tdmcp

tdmcp

by lucasmaher-hash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create colour palette / gradient

create_palette

Create a reusable colour palette and gradient from a base hue or sampled image, outputting swatches as channels for downstream colour tools.

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).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_palette"
  }
}

Input 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
nameNoBase name for the created nodes.palette
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).
valueNo(harmony) Base value / brightness 0..1.
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.
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).
parent_pathNoCOMP to build the Ramp TOP + swatch CHOP inside./project1
expose_controlsNoAdd BaseHue / Saturation / Value / Rule / Count custom parameters to parent_path.
analogous_spreadNo(harmony, analogous rule) Hue step between neighbours, 0..0.5 (0.083 ≈ 30°).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.1

TDQS

A4.3/5.0
Behavior4/5

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

The description states what it builds (Ramp TOP gradient, Constant CHOP with swatch{i}r/g/b channels), that live controls are exposed on the parent, and that it builds standalone. This goes beyond the readOnlyHint/destructiveHint annotations and provides useful behavioral context, though it does not discuss permissions or edge cases like fallback behavior from the schema.

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 a single dense paragraph but every sentence adds value: modes, outputs, downstream usage, live controls, standalone nature. No fluff, appropriately sized for the tool's complexity.

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?

For an 11-parameter tool with no output schema, the description covers the core concept, modes, generated artifacts, and integration targets. It leverages the schema for parameter details and the annotations for safety flags, so it is complete enough for an agent to decide when and how to use it.

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

Parameters3/5

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

The input schema already provides 100% parameter descriptions, so the description adds little beyond what the schema states. It does clarify the conceptual relationship between modes and parameters (e.g., base_hue, rule, count) and mentions the exposed controls, but no new parameter syntax or semantics beyond schema.

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 'Generate a reusable colour palette + gradient other tools can bind to,' which is a specific verb+resource. It distinguishes two modes ('harmony' vs 'from_source') and names downstream consumers (create_color_grade, generate_from_moodboard, bind_to_channel), making it distinct from sibling tools.

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?

It explains when to use each mode (harmony for computed swatches, from_source for sampling a TOP) and notes that a harmony palette is standalone. However, it does not explicitly name alternative tools or exclusion cases, so it is clear but not maximally explicit.

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