Skip to main content
Glama
Sign In

Colour Memory

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

Lock-and-Fill Palette from Archive

palette_generate
Read-only

Send a palette of up to 12 slots, locking some with hex values and leaving others empty. Empty slots are filled with the nearest CIEDE2000 archive match, interpolated from the locked anchors. Optional archive filter restricts fills to one archive. Returns full citation (name, archive, primary source, colour notes) for every filled slot. Example: lock a client's existing wall colour and fill a 5-colour scheme from Oxfordshire. 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": {
      "slots": "<slots>"
    },
    "name": "palette_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoTotal CURATED palette size 2-12 (default 5). This is the designed-palette ceiling, not a product limit on how many colours exist: for a large colour COLLECTION, page archive_search instead.
slotsYesList of palette slots. Each has index (0-11), optional hex, and locked flag.
archiveNoOptional: restrict fills to one archive e.g. 'Oxfordshire', 'Shakespeare', 'Japan'

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / size / description
      Previous value: -"Total palette size 2-8 (default 5)"New value: +"Total CURATED palette size 2-12 (default 5). This is the designed-palette ceiling, not a product limit on how many colours exist: for a large colour COLLECTION, page archive_search instead."
    • changedInput schema / properties / slots / description
      Previous value: -"List of palette slots. Each has index (0-7), optional hex, and locked flag."New value: +"List of palette slots. Each has index (0-11), optional hex, and locked flag."
    • changedInput schema / properties / slots / items / properties / index / description
      Previous value: -"Slot position 0-7"New value: +"Slot position 0-11"
  2. 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"
+}
  3. 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
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "error": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "result": {
+      "type": [
+        "object",
+        "array",
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  5. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations supply only readOnlyHint, so the description carries most of the burden and does so: it discloses that fills are interpolated from locked anchors, that an optional filter can restrict fills to one archive, that each filled slot returns a full citation (name, archive, primary source, colour notes), and that the result already contains the rendered palette with PNG, PDF, ASE, JSON and CSS downloads. The evidence-versus-recommendation caveat is exactly the kind of semantic guardrail annotations cannot express.

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 lock-and-fill mechanic is front-loaded and the example is compact. The closing two sentences about evidence versus recommended colours and registering with palette_finalize overlap somewhat and could be tightened, but neither is filler since they define the handoff.

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 explain return values, yet it still characterizes the citation payload and the download bundle. Combined with the explicit palette_finalize handoff, an agent has enough to invoke and follow up correctly; only explicit error or edge-case behavior (e.g., hex required when locked) is left to the schema.

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 baseline is 3; the description adds real meaning by explaining how slots interact (locked slots are fixed and excluded from filling, empty ones are interpolated from the anchors) and what archive filtering does. The size and archive parameters are left largely to the schema, which already documents them well.

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 states a specific verb and mechanism: send a palette of up to 12 slots, lock some with hex, leave others empty, and have empties filled by nearest CIEDE2000 archive match interpolated from the locked anchors. That is far more than the title restates and makes the tool distinguishable from palette_export or archive_search.

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 gives a concrete usage scenario (lock a client's existing wall colour and fill a 5-colour scheme from Oxfordshire) and routes follow-on work to palette_finalize, explicitly warning that archive anchors are evidence rather than the recommended colours. It stops short of stating outright when not to use this tool, so it is strong context rather than a full when/when-not/alternative map.

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