Colour Memory

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

Generate Heritage Palette from Cultural Concept

palette_concept

Read-only

Generate a historically grounded colour palette from a cultural concept or theme. Returns 4-6 coordinated archive colours with hex values, proportions, and provenance. Examples: 'Victorian mourning', 'Ottoman court', 'Japanese wabi-sabi', 'Scandinavian winter', 'West African kente', 'Renaissance Florence'. Every colour returned is sourced from the archive with documented history. 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": {
      "concept": "<concept>"
    },
    "name": "palette_concept"
  }
}

Input Schema

Name	Required	Description
`avoid`	No	Colours, pigments or topics to exclude e.g. ['arsenic green']. Applied before selection.
`concept`	Yes	Cultural theme or historical period e.g. 'Victorian mourning' or 'Ottoman court'
`n_colours`	No	Number of colours to return (default 5, max 8)
`include_neutrals`	No	Include neutral/background colours

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 21, 2026

addedInput schema / properties / avoid

Added value: +{
+  "default": [],
+  "description": "Colours, pigments or topics to exclude e.g. ['arsenic green']. Applied before selection.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

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

AddedJun 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the load: it discloses that 4-6 colours are returned with hex, proportions and provenance, that every colour is archive-sourced, and that the result already bundles rendered palette plus PNG/PDF/ASE/JSON/CSS downloads. The caveat that anchors are evidence rather than recommendations is valuable behavioural context. Minor gap: no mention of limits or failure modes when a concept yields too few archive matches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and examples, which is good, but the middle is padded with a long list of example themes and the final two sentences about evidence versus recommendation are convoluted and take work to parse. Several sentences could be tightened without losing meaning.

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, yet the description usefully explains what the result practically contains (rendered palette and multiple download formats) and how it feeds palette_finalize, which is the key workflow information an agent needs. It is nearly complete for a read-only generation tool, with only edge-case behaviour unaddressed.

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 coverage is 100%, so all four parameters are already documented, and the baseline of 3 applies. The description adds little beyond the schema for parameters; the concept examples overlap with the schema's own examples, and avoid/n_colours/include_neutrals are not discussed in the description text.

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 and resource ('Generate a historically grounded colour palette from a cultural concept') and distinguishes itself from palette_finalize, which is named as the finalizing step. The examples of concepts make the input domain concrete.

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?

Clearly positions this as the evidence-gathering step and names palette_finalize as the downstream call 'called once with those exact colours'. It explains that archive anchors are evidence, not the recommended colours, which implies when to move on. It does not explicitly exclude sibling tools such as palette_heritage or palette_generate, so it falls short of a 5.

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?