Skip to main content
Glama
Sign In

Designers

by com.allthepossibles
OverviewDiscussionsAdmin

Palette harmony

palette_harmony
Read-only

Build color harmonies from base colors. Pass colors (one to six colors as hex, rgb(), hsl() or CSS names, comma or newline separated, or an array) and optionally harmony (complementary, analogous, triadic, split-complementary or tetradic) to return one scheme. Hue is rotated in OKLCH with lightness and chroma held, so the set is evenly weighted; colors that cannot hold the chroma inside sRGB are reduced and marked. Returns hex and oklch() for each color, a note on which harmony suits which job, and a list of near-duplicates (OKLab distance under 3, a working convention). Near-gray bases have no hue and are flagged. OKLCH opposites differ from the red-yellow-blue paint wheel. Pure maths, nothing stored.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "colors": "<colors>"
    },
    "name": "palette_harmony"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorsYesOne to six base colors: a string such as "#1b3a5c, #e4572e" or an array of strings.
harmonyNoReturn only this harmony. Omit for all five.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / colors / description
      Previous value: -"One to six base colours: a string such as \"#1b3a5c, #e4572e\" or an array of strings."New value: +"One to six base colors: a string such as \"#1b3a5c, #e4572e\" or an array of strings."
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only and closed-world annotations, the description discloses substantial behavior: OKLCH hue rotation with lightness and chroma held, chroma reduction inside sRGB, hex and oklch() return values, near-duplicate detection, and near-gray base handling. It also clarifies that the operation is pure math and stores nothing.

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?

The description is dense but well front-loaded: the core purpose appears first, followed by input, processing, and output details. The length is justified by the tool's specialized color behavior, though a few clauses could be tightened.

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?

With no output schema, the description carries the burden of explaining return values and does so: it lists hex and oklch() output, harmony suitability notes, and near-duplicate reporting. It also covers relevant edge cases such as out-of-sRGB chroma and near-gray bases, making it complete for correct invocation.

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%, so the baseline is 3. The description still adds useful semantic detail beyond the schema, including accepted color formats (hex, rgb(), hsl(), CSS names) and comma/newline separation, though it also repeats some schema-level information such as the one-to-six color range.

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 the specific action and resource: build color harmonies from base colors. It is easy to tell what the tool does, but it does not explicitly distinguish itself from nearby palette-related siblings such as tint_shade_scale or colour_temperature_mix.

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

Usage Guidelines3/5

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

The description implies usage by explaining that you pass colors and optionally a harmony to return one scheme. It does not state when to use this versus alternatives, nor when not to use it, leaving selection guidance to inference.

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

All Designers toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources