Colour Memory

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

Analyse Palette Against Archive

palette_analyse

Read-only

Analyse a palette of hex colours against the Colour Memory archive. For each colour returns the nearest named archive entry with cultural name, source, claim_strength (A-E), do_not_say guardrails, and alternatives when confidence is low. Palette-level deduplication ensures no two colours map to the same archive entry. Use after extracting colours from a photo or generating a palette. 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": {
      "colours": "<colours>"
    },
    "name": "palette_analyse"
  }
}

Input Schema

Name	Required	Description
`n`	No	Max alternatives per colour when confidence is low (1-3, default 1)
`archive`	No	Optional: restrict to one archive e.g. China, Pigment, ArtsAndCrafts
`colours`	Yes	Array of colour objects

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedJun 27, 2026

TDQS

A4.4/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 burden, and it does add real behavioral context: palette-level deduplication guarantees no two colours map to the same entry, alternatives are only produced when confidence is low, and the response bundles rendered palette plus PNG/PDF/ASE/JSON/CSS downloads. What it does not cover is cost, latency, or limits on palette size.

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 purpose and return shape, then usage, then the palette_finalize handoff — a sensible order. The closing clause about the customer seeing and downloading what was actually recommended repeats the earlier download sentence and could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 still gives an agent enough to call it correctly and to know what to do next with the result. For a read-only analysis tool with three documented parameters, nothing material is missing.

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 the schema already documents n, archive and the colour objects. The description adds meaning for the alternatives parameter ('alternatives when confidence is low') but never explains the archive restriction or what weight does, leaving it at the baseline for a fully documented schema.

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 ('Analyse a palette of hex colours against the Colour Memory archive') and immediately enumerates what comes back per colour (nearest named entry, cultural name, source, claim_strength A-E, guardrails, alternatives). It also distinguishes itself from palette_finalize, which registers the chosen palette rather than analysing evidence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Use after extracting colours from a photo or generating a palette') and an explicit downstream handoff ('A final palette chosen from this evidence is registered with palette_finalize, called once with those exact colours'). It also states a usage boundary: the archive anchors are evidence, not the recommended colours.

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?