Skip to main content
Glama

Colour Memory

by com.colourmemory.api
OverviewDiscussionsAdmin

Translate Any Palette into a Named Archive

palette_translate
Read-only

Map any list of hex values into a target archive using CIEDE2000 nearest-neighbour matching. Each input hex is matched to the closest named colour in the chosen archive, with a delta-e relevance band (exact / close / approximate / loose) and full provenance. Use to translate a client's paint colours into Shakespeare language, map a brand palette into historical Japanese pigments, or find the nearest Oxfordshire equivalents to a French scheme. The result already carries the rendered palette and its PNG, PDF, ASE, JSON and CSS downloads -- show them to the customer. Never present the archive anchors a colour was derived from as the colours you are recommending. If you go on to choose a final palette OF YOUR OWN from this evidence, call palette_finalize once with those exact colours so the customer can see and download what you actually recommended.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paletteYesList of hex values to translate e.g. ['#F5F0E8', '#8B6B3D']
max_delta_eNoMax acceptable CIEDE2000 distance — above this is flagged out-of-threshold (default 40)
target_archiveYesArchive to translate into e.g. 'Shakespeare', 'Japan', 'Oxfordshire'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / palette / description
      Previous value: -"List of up to 24 hex values to translate e.g. ['#F5F0E8', '#8B6B3D']"New value: +"List of hex values to translate e.g. ['#F5F0E8', '#8B6B3D']"
  2. Changed2 schema fields changed
    • changedInput schema / properties / palette / description
      Previous value: -"List of hex values to translate e.g. ['#F5F0E8', '#8B6B3D']"New value: +"List of up to 24 hex values to translate e.g. ['#F5F0E8', '#8B6B3D']"
    • addedInput schema / properties / palette / maxItems
      Added value: +24
  3. 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"
+}
  4. 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
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, so safety is covered. The description adds rich behavior beyond that: the delta-e relevance band (exact/close/approximate/loose), full provenance, and the fact that the result already carries rendered palette plus PNG, PDF, ASE, JSON and CSS downloads. It does not contradict the read-only annotation.

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 core mechanism, then use cases, then output and routing guidance. Dense and every sentence carries actionable content, though the multi-clause run-on sentences make it longer than strictly necessary.

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?

An output schema exists, so return values need not be restated, yet the description usefully notes the result carries rendered palette and export downloads. For a read-only convenience tool with a clear sibling hand-off to palette_finalize, nothing an agent needs to invoke it correctly is missing.

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, but the description adds semantics not in the schema: what the matching metric actually does (CIEDE2000 nearest-neighbour) and what the delta-e thresholds mean qualitatively (exact/close/approximate/loose), which is the meaningful context for tuning max_delta_e.

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?

States a specific verb+resource: mapping a list of hex values into a named archive via CIEDE2000 nearest-neighbour matching, with an explicit output (delta-e band + provenance). This is clearly distinguishable from siblings like palette_compare, colour_match_paint, or archive_search, which operate by different matching logic.

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

Usage Guidelines5/5

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

Gives three concrete when-to-use scenarios (client paint colours into Shakespeare, brand palette into Japanese pigments, French scheme to Oxfordshire) and explicitly routes the agent onward: call palette_finalize once with the final autonomous choice. It also states a when-not-to: never present archive anchors as the recommended colours.

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

All Colour Memory 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