Skip to main content
Glama
Colors MCP Server

Colors MCP Server

by HtetOoWaiYan

Find colors that meet rules

colors_find
Read-onlyIdempotent

Find verified hex colors that satisfy combined hue, chroma, lightness, background contrast, and color-difference rules in one call; returns colors with margin or identifies the unmet rule.

Instructions

Find colors that satisfy your rules in one call. Combine any of: hue band (or the hue family of a color), chroma range, lightness range, contrast against one or more backgrounds (against), and for several colors a minimum lightness gap, hue gap or color difference (optionally color-blind safe). Returns verified hex colors with the most margin, or says which rule cannot be met.

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": "colors_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
cvdNoSeveral colors: also keep every pair apart (minDeltaE) under this color blindness. "all" covers the three common types. Default "none".none
countNoHow many colors to find. Default 1.
hueOfNoInstead of hueMin/hueMax: keep the found colors in the hue family of this color (for example the brand color). The band is its OKLCH hue plus or minus hueWithin.
hueMaxNoOKLCH hue band end, degrees 0-360.
hueMinNoOKLCH hue band start, degrees 0-360 (red 30, yellow 100, green 145, cyan 200, blue 260, purple 305, pink 350). If hueMin is above hueMax the band wraps through 0.
againstNoEvery found color must reach the ratio against each of these colors, for example a light and a dark surface.
chromaMaxNoMaximum OKLCH chroma.
chromaMinNoMinimum OKLCH chroma (0 gray, 0.1 muted, 0.2 vivid).
hueWithinNoDegrees either side of hueOf. Default 20.
minDeltaENoSeveral colors: minimum CIEDE2000 difference between every pair. Default 15 when no other pair rule is given.
minHueGapNoSeveral colors: minimum OKLCH hue difference in degrees between every pair of colorful colors.
lightnessMaxNoMaximum OKLCH lightness.
lightnessMinNoMinimum OKLCH lightness, 0 black to 1 white.
minLightnessGapNoSeveral colors: minimum OKLab lightness difference between every pair (keeps them apart in grayscale).

Output Schema

NameRequiredDescriptionDefault
foundYes
pairsNo
colorsYes
detailsNo
allRulesHoldYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety needs no restating. The description adds genuinely new behavior: it returns hex colors chosen "with the most margin" (an optimization objective, not just feasibility) and reports "which rule cannot be met" on failure, which is the key non-obvious outcome for a solver. It stops short of describing output structure or how margin is traded off among competing rules.

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?

Two sentences, front-loaded with the purpose and then the constraint inventory; every clause maps to a parameter family, and the return/failure sentence is last where it belongs. The middle sentence is heavily compressed with nested parentheticals, which costs a little readability, but nothing is redundant.

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

Completeness4/5

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

For a 14-parameter solver with full schema coverage, an output schema, and complete annotations, the description covers purpose, the combinable rule set, the pairwise-only condition, and the success/failure outcome. The only missing piece is how conflicting rules are resolved or which rule is prioritized when several fail, which is a minor gap given the output schema can carry the result shape.

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 earns above baseline by grouping the 14 parameters into named rule families (hue band or hue family, chroma range, lightness range, contrast against backgrounds, pairwise gaps) and by flagging the interaction that pair rules only apply "for several colors" and that color-blind safety is an optional modifier on them. That conceptual map is not in the schema, where the parameters appear as a flat undifferentiated list.

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?

"Find colors that satisfy your rules" gives a specific verb (find) and resource (colors) plus the core mechanism (satisfy rules), and the following clause enumerates the constraint families so an agent knows exactly what class of problem this solves. It does not name or contrast any sibling (e.g. colors_palette, colors_harmony, colors_check), so an agent must infer the boundary itself.

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?

"in one call" and "Combine any of: ..." imply this is the batch constraint-solver rather than chaining check/fix, and the conditional framing "for several colors a minimum ... gap" signals when pair rules apply. However, there is no explicit when-to-use/when-not statement and no named alternative for the adjacent tasks (auditing an existing palette, harmonizing from a base color), leaving the routing decision implicit.

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