Colour Memory

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

Compare Two Palettes

palette_compare

Read-only

Deep perceptual, cultural, and commercial comparison between two palettes. Returns timelessness scores, commercial strength, cultural depth, emotional difference, and a winner verdict for the stated use case. The result already carries the rendered palette and its PNG, PDF, ASE, JSON and CSS downloads, ready to show the customer. The archive anchors a colour was derived from are evidence, not the recommended colours. A final palette chosen from this evidence is registered with palette_finalize, called once with those exact colours, so the customer can see and download what was actually recommended.

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": {
      "palette_a": "<palette_a>",
      "palette_b": "<palette_b>"
    },
    "name": "palette_compare"
  }
}

Input Schema

Name	Required	Description
`markets`	No	Target markets
`use_case`	No	Context for comparison e.g. luxury packaging
`palette_a`	Yes	First palette hex values
`palette_b`	Yes	Second palette hex values

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 20, 2026

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"
+}

Changed1 schema field changedJun 17, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "error": {
-      "type": "string"
-    },
-    "ok": {
-      "type": "boolean"
-    },
-    "result": {
-      "type": [
-        "object",
-        "array",
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

AddedMay 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The readOnlyHint=true annotation is consistent with a comparison tool, so the safety bar is already met by structured data. The description adds real context beyond it: the result carries the rendered palette plus PNG, PDF, ASE, JSON and CSS downloads 'ready to show the customer', and it clarifies that archive anchors are supporting evidence rather than outputs. It does not discuss cost, latency, or length limits on the comparison.

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 purpose and returned scores are front-loaded, and each sentence carries a distinct piece of information (outputs, artifacts, evidence caveat, finalize handoff). The sentence 'The archive anchors a colour was derived from are evidence' is grammatically awkward and the finalize workflow could be tightened, keeping it below a 5.

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 an output schema present, the description need not restate every return field, and it instead covers the pieces the schema cannot: the downloadable artifacts and the palette_finalize handoff. An agent knows how to call it and what to do with the result. Minor gaps remain around how many colours each palette should contain and how markets affect the verdict.

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 four parameters (markets, use_case, palette_a, palette_b) are already documented. The description only echoes use_case indirectly via 'for the stated use case' and says nothing about markets or expected palette length/format, so it adds little beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Deep perceptual, cultural, and commercial comparison between two palettes') and enumerates the outputs (timelessness, commercial strength, cultural depth, emotional difference, winner verdict). It does not distinguish itself from the closest siblings such as colour_compare or palette_verdict, so an agent still has to guess between similar comparison 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?

Gives clear downstream context: this produces evidence, and the recommended colours must be registered via palette_finalize 'called once with those exact colours'. It also warns that archive anchors are evidence, not recommendations. It stops short of explicit when-not-to-use conditions or naming the alternative comparison tools.

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

All Colour Memory tools Inspect

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

Need Help?