Skip to main content
Glama
Sign In

Colour Memory

by app.railway.up.colour-memory-api-production
OverviewDiscussionsAdmin

Colour Passport -- Complete Colour Truth Object

colour_passport
Read-only

Canonical single-call colour truth object. Returns everything known about a hex value: colour science (Lab, LCh, hue, chroma, depth, temperature, LRV), archive anchor with dE2000, claim_strength, do_not_say and evidence grade, hex provenance (status, confidence, spectrophotometric flag), physics (illuminant behaviour, gamut, print risk), and cultural reading (colour family, warnings, positives). This is the foundation call for the complete picture of one colour. Every other tool is built on this data. Replaces chaining colour_dna + archive_provenance + colour_cultural_risk + colour_metrics separately. Examples: '#31559B' (anchors to Henry VIII Manuscript Blue Initials), '#8B1A1A' (Penny Post Sealing Wax Dark Red), '#D4AF37' (Sutton Hoo Great Gold Buckle).

Input Schema

NameRequiredDescriptionDefault
hexNoSingle hex colour e.g. #31559B
hexesNoMultiple hex colours for batch lookup e.g. ['#31559B', '#8B1A1A']. Max 20.
n_archiveNoNumber of archive matches to return (default 3)
include_physicsNoInclude illuminant behaviour and gamut data (default true)
include_culturalNoInclude cultural risk and associations (default true)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "hex"
+    ]
+  },
+  {
+    "required": [
+      "hexes"
+    ]
+  }
+]
    • changedInput schema / properties / hex / description
      Previous value: -"Hex colour e.g. #31559B"New value: +"Single hex colour e.g. #31559B"
    • addedInput schema / properties / hexes
      Added value: +{
+  "description": "Multiple hex colours for batch lookup e.g. ['#31559B', '#8B1A1A']. Max 20.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / required
      Removed value: -[
-  "hex"
-]
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=true, so the safety profile is covered, and the description adds useful context about the depth and provenance-grading of the returned data. It does not disclose batch behaviour limits, cost/latency characteristics of a multi-domain lookup, or what happens when a hex has no archive anchor despite the claim_strength/evidence-grade framing.

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 claim and a compact enumeration of returned domains, followed by differentiation and concrete examples. There is some redundancy in 'This is the foundation call for the complete picture of one colour. Every other tool is built on this data,' which restates the opening line without adding new information.

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?

An output schema exists, so the description needn't explain return values, and it does cover purpose, replacements, and example inputs. The main omission is the relationship to the plural sibling colour_passports and the batch semantics, which an agent choosing between the two would need.

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%, so all five parameters are already documented, including n_archive, include_physics, and include_cultural defaults. The description adds only illustrative hex examples with their archive anchors; it does not clarify the single-vs-batch (hex vs hexes) selection or the interaction between the include flags.

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 identity ('Canonical single-call colour truth object') and enumerates the exact domains returned (colour science, archive anchor with dE2000, hex provenance, physics, cultural reading). It explicitly distinguishes itself from siblings by naming the four tools it replaces, so an agent can tell what it does without opening the 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?

It clearly states the usage condition ('foundation call for the complete picture of one colour') and names the alternatives it supersedes (colour_dna, archive_provenance, colour_cultural_risk, colour_metrics). However, it gives no guidance on when NOT to use it, notably the existence of the plural sibling colour_passports and the hexes batch path (max 20) described only in the schema.

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