Colour Memory

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

Archive Report Brief

archive_report_brief

Read-only

One-call complete archive research package for a document, PDF, or editorial brief. Input: title, audience, themes, archives to draw from, things to avoid, number of colours. Output: ranked colour cards with full provenance, story order, source confidence flags, pull quote, CTA line, CSS tokens, image prompt for Midjourney/Flux/DALLE, editorial argument, weakest and strongest entries identified. Replaces chaining archive_search + get_colour_card + cliche_breaker + agent_brief separately. Two Claude calls total. This is the endpoint for building premium archive documents, PDFs, briefs, and editorial content. Use this first for any document workflow.

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": {
      "themes": "<themes>"
    },
    "name": "archive_report_brief"
  }
}

Input Schema

Name	Required	Description
`avoid`	No	Topics to suppress e.g. ['arsenic wallpaper', 'Wedgwood blue']
`title`	No	Document title e.g. 'The Colours of Georgian Power'
`themes`	Yes	Research themes e.g. ['racing silks', 'EIC trade', 'Keats']
`archives`	No	Archives to search e.g. ['RacingSilks', 'EIC', 'Keats', 'Dickens']
`audience`	No	Target audience e.g. 'serious Georgian collector'
`n_colours`	No	Number of colours to return (default 8, max 16)
`period_end`	No	Hard period gate: exclude entries dated after this year. Default 9999 (no upper bound).
`period_start`	No	Hard period gate: exclude entries dated before this year. Default 0 (no lower bound).
`allow_partial`	No	If false (default), returning fewer cards than requested sets ok=false with error_code INSUFFICIENT_PALETTE_RESULTS instead of a silent short 'success'. Set true to accept a short result.
`output_format`	No	Reserved for future use -- currently accepted but has no effect on the response shape (the endpoint always returns the full report).
`strict_sources`	No	Only return entries with named primary sources (default true)
`family_card_mode`	No	How near-identical cultivars/records are presented. 'auto' (default): current behaviour, groups into family cards above the standard Delta E threshold. 'always': widens the clustering threshold so more near-duplicates group into family cards. 'conservative': suppresses family cards over max_family_card_share of the deck, instead promoting one hero cultivar per suppressed family with the rest folded into that card's also_supported_by list (never dissolved back into separate near-duplicate swatches).
`confidence_threshold`	No	Minimum confidence score (0.0-1.0) for an entry to be included. Default 0.5 filters out weakly-matched stubs.
`max_family_card_share`	No	Conservative mode only: maximum fraction (0.0-1.0, default 0.5) of presented cards that may be family cards before excess families are suppressed to hero cards. Ignored in auto/always modes.
`minimum_claim_strength`	No	Hard evidence-grade floor: A, B, C, D, or E. Never silently relaxed.
`strict_semantic_colour`	No	Default false. When true, excludes entries whose quoted colour language contradicts their stored hex (e.g. a record naming 'Prussian blue' whose hex is actually a pale cream) rather than presenting them as normal evidence. Never alters hex values, only excludes flagged ones.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / family_card_mode / description

Previous value: -"How near-identical cultivars/records are presented. 'auto' (default): current behaviour, groups into family cards above the standard ΔE threshold. 'always': widens the clustering threshold so more near-duplicates group into family cards. 'conservative': suppresses family cards over max_family_card_share of the deck, instead promoting one hero cultivar per suppressed family with the rest folded into that card's also_supported_by list (never dissolved back into separate near-duplicate swatches)."New value: +"How near-identical cultivars/records are presented. 'auto' (default): current behaviour, groups into family cards above the standard Delta E threshold. 'always': widens the clustering threshold so more near-duplicates group into family cards. 'conservative': suppresses family cards over max_family_card_share of the deck, instead promoting one hero cultivar per suppressed family with the rest folded into that card's also_supported_by list (never dissolved back into separate near-duplicate swatches)."

Changed1 schema field changedAug 3, 2026

addedInput schema / properties / strict_semantic_colour

Added value: +{
+  "description": "Default false. When true, excludes entries whose quoted colour language contradicts their stored hex (e.g. a record naming 'Prussian blue' whose hex is actually a pale cream) rather than presenting them as normal evidence. Never alters hex values, only excludes flagged ones.",
+  "type": "boolean"
+}

Changed7 schema fields changedAug 2, 2026

addedInput schema / properties / allow_partial

Added value: +{
+  "description": "If false (default), returning fewer cards than requested sets ok=false with error_code INSUFFICIENT_PALETTE_RESULTS instead of a silent short 'success'. Set true to accept a short result.",
+  "type": "boolean"
+}

addedInput schema / properties / confidence_threshold

Added value: +{
+  "description": "Minimum confidence score (0.0-1.0) for an entry to be included. Default 0.5 filters out weakly-matched stubs.",
+  "type": "number"
+}

addedInput schema / properties / family_card_mode

Added value: +{
+  "description": "How near-identical cultivars/records are presented. 'auto' (default): current behaviour, groups into family cards above the standard ΔE threshold. 'always': widens the clustering threshold so more near-duplicates group into family cards. 'conservative': suppresses family cards over max_family_card_share of the deck, instead promoting one hero cultivar per suppressed family with the rest folded into that card's also_supported_by list (never dissolved back into separate near-duplicate swatches).",
+  "enum": [
+    "auto",
+    "always",
+    "conservative"
+  ],
+  "type": "string"
+}

addedInput schema / properties / max_family_card_share

Added value: +{
+  "description": "Conservative mode only: maximum fraction (0.0-1.0, default 0.5) of presented cards that may be family cards before excess families are suppressed to hero cards. Ignored in auto/always modes.",
+  "type": "number"
+}

addedInput schema / properties / output_format

Added value: +{
+  "description": "Reserved for future use -- currently accepted but has no effect on the response shape (the endpoint always returns the full report).",
+  "type": "string"
+}

addedInput schema / properties / period_end

Added value: +{
+  "description": "Hard period gate: exclude entries dated after this year. Default 9999 (no upper bound).",
+  "type": "integer"
+}

addedInput schema / properties / period_start

Added value: +{
+  "description": "Hard period gate: exclude entries dated before this year. Default 0 (no lower bound).",
+  "type": "integer"
+}

Changed1 schema field changedJul 13, 2026

addedInput schema / properties / minimum_claim_strength

Added value: +{
+  "description": "Hard evidence-grade floor: A, B, C, D, or E. Never silently relaxed.",
+  "type": "string"
+}

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.1/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 usefully adds cost/orchestration behavior: 'Two Claude calls total' and consolidation of four separate tools into one call. It does not state latency expectations, caching, or what happens when the two-call budget is exceeded. No contradiction with the read-only annotation, since the tool composes research rather than mutating stored state.

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?

Purpose is front-loaded in the first clause, followed by Input/Output blocks and the routing sentence. The long Output enumeration is partly redundant given a dedicated output schema exists, but it is dense and information-bearing rather than padded.

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?

For a 16-parameter tool with an output schema and thin annotations, the description covers purpose, consolidation value, call budget, and the shape of the return. The main omission is differentiating from archive_report_document and clarifying behavior when only the required 'themes' argument is supplied, so it is strong but not fully complete.

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 every parameter (including the subtle allow_partial, strict_semantic_colour, family_card_mode, and the two period gates) is already fully documented in the schema. The description only restates a handful of those inputs ('title, audience, themes, archives, things to avoid, number of colours'), adding no meaning beyond the structured data. Baseline 3 is appropriate.

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 names a specific verb and artifact ('One-call complete archive research package for a document, PDF, or editorial brief') and enumerates the concrete deliverables: ranked colour cards with provenance, story order, confidence flags, pull quote, CTA, CSS tokens, image prompt, and editorial argument. An agent can tell exactly what this produces 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 gives explicit routing guidance -- 'Replaces chaining archive_search + get_colour_card + cliche_breaker + agent_brief separately' and 'Use this first for any document workflow' -- which is strong when-to-use signal. It stops short of saying when NOT to use it, and it never addresses the near-twin sibling archive_report_document, leaving a real ambiguity unresolved.

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?