Skip to main content
Glama

Compare Two Colours: Perceptual and Cultural

colour_compare
Read-only

Deep perceptual and semantic comparison between any two hex values. Returns quantified differences in LRV, chroma, hue angle, warmth, and CIEDE2000 distance, plus cultural context on both: which is more authoritative, more saturated, more stable under different illuminants, and what each has historically signified. Use when choosing between two colours or explaining why one works better than another. Not a harmony tool; this is a decision and reasoning tool.

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": {
      "hex_a": "<hex_a>",
      "hex_b": "<hex_b>"
    },
    "name": "colour_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
hex_aYesFirst colour hex e.g. '#003366'
hex_bYesSecond colour hex e.g. '#1877F2'

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Structured JSON response. Shape varies by tool; most return an 'ok' boolean plus a 'result' or 'results' field with the tool's data payload.",
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "error": {
      -      "type": "string"
      -    },
      -    "ok": {
      -      "type": "boolean"
      -    },
      -    "result": {
      -      "type": [
      -        "object",
      -        "array",
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description goes well past that by disclosing the analysis output types and that cultural interpretation for both colours is included. It does not say how invalid or malformed hex values are handled, nor whether the cultural commentary is optional or always computed, which are the remaining behavioral unknowns.

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?

Front-loaded with the purpose and outputs, then closes with usage and exclusion. It is dense but slightly overloaded by the cultural-context clause, which lists four separate interpretive claims in one sentence and could be tightened.

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?

With a rich output schema and full parameter documentation, the description only needs to cover selection and scope, and it does both. An agent knows when to pick this over harmonies and roughly what answer shape to expect; handling of edge cases like invalid input is the only omission.

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?

Schema description coverage is 100% with two required hex parameters already given example values, so the schema carries parameter meaning. The description adds only the word "any" (i.e., no palette or named-colour constraint), staying at the baseline for a fully documented 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?

Opens with a specific verb+resource pair ("deep perceptual and semantic comparison between any two hex values") and enumerates the concrete dimensions returned (LRV, chroma, hue angle, warmth, CIEDE2000). It also distinguishes itself from the harmony family, so an agent can separate it from colour_harmonies or palette_compare without opening a schema.

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?

Gives an explicit use condition ("when choosing between two colours or explaining why one works better than another") plus an explicit exclusion ("Not a harmony tool; this is a decision and reasoning tool"). The gap is that it names no concrete sibling to route to, so an agent must infer the alternative from context rather than being told.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources