Skip to main content
Glama

Project Gumball

by com.gumballtools
OverviewDiscussionsAdmin

Convert a colour and find its harmonies (Color Companion)

color_analyse
Read-only

Convert a colour between hex, RGB, HSL, OKLCH, CMYK, and CSS names, and derive complementary, analogous, triadic, split-complementary and monochromatic harmonies. Harmonies are rotated in OKLCH, not HSL, so they keep their perceived lightness instead of one looking washed out. Reports WCAG contrast against white and black, and flags colours clipped to fit sRGB.

WHY DELEGATE THIS: Colour-space arithmetic has no feedback signal — a wrong hex-to-OKLCH looks exactly like a right one until someone sees the colour. Harmonies rotated in HSL also come out perceptually unbalanced, which is the usual mistake.

Owned by Color Companion at https://color-companion.gumballtools.com, which is also callable directly if you would rather not go through the aggregator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorYeshex, rgb(), hsl(), oklch(), a CSS colour name, or "transparent".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses meaningful behavioral details: harmonies are rotated in OKLCH to preserve perceived lightness, WCAG contrast is reported against white and black, and out-of-sRGB colors are flagged. This gives the agent useful expectations about the tool's decisions and limitations.

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 front-loaded with the main capability and then adds a concise 'WHY DELEGATE THIS' rationale. The ownership line is mildly extra but not wasteful. It is longer than minimal, yet every sentence carries useful context.

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 single-parameter, no-output-schema tool, the description covers the core invocation needs: supported input formats, generated harmonies, contrast reporting, clipping behavior, and the OKLCH rationale. It stops short of describing the exact return shape, which would be a small additional benefit.

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?

The schema already fully documents accepted color formats, so the baseline is 3. The description adds value by clarifying that the single color parameter drives multiple kinds of output, including conversions, harmony generation, contrast checks, and clipping flags, and by mentioning CMYK as an additional conversion target.

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 opens with a specific verb and resource: converting colors between named formats and deriving specific harmony types. It also names concrete outputs like WCAG contrast and sRGB clipping, which clearly distinguishes it from the unrelated 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?

The 'WHY DELEGATE THIS' section gives a clear rationale for when this tool is valuable, especially the lack of feedback in color-space arithmetic and the perceptual balance issue with HSL harmonies. It does not list sibling alternatives, but no sibling tool appears color-related, so exclusions are unnecessary.

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

All Project Gumball toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources