Skip to main content
Glama

Archive Gradient: Lab-Interpolated Colour Journey

palette_gradient
Read-only

Generate a perceptually smooth gradient between 2-5 archive anchor colours. Each interpolated stop snaps to the nearest real archive colour by CIEDE2000. Anchor stops are kept true to their source. Choose linear (physically accurate Lab interpolation) or chroma_preserved (LCh interpolation, short-arc hue, avoids desaturated midpoints). Returns stop array, CSS linear-gradient string, or SVG swatch bar. Use for design briefs, colour journey visualisations, and gradient systems. 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": {
      "anchors": "<anchors>"
    },
    "name": "palette_gradient"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNolinear: straight Lab lerp (may have neutral midpoint). chroma_preserved: LCh short-arc, saturation maintained.chroma_preserved
stepsNoTotal stops including anchors (default 7, max 20)
anchorsYes2-5 hex values (#RRGGBB) or exact archive colour names
archiveNoRestrict snapping to this archive name e.g. Victorian
output_formatNostops: array of colour objects. css: linear-gradient string. svg: swatch bar.stops
snap_to_archiveNoSnap each stop to nearest archive colour (default true)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      +}
  2. 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
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

With readOnlyHint=true covering safety, the description adds substantial behavioral detail: snapping uses CIEDE2000, anchors are preserved, linear vs chroma_preserved interpolation differ, and outputs can be stops, CSS, or SVG. It further states that results carry rendered palette and PNG/PDF/ASE/JSON/CSS downloads, which is useful context beyond the annotation.

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 definition is front-loaded and well organized: generation, snapping/interpolation, outputs, use cases, then handoff to palette_finalize. The second half is somewhat verbose and repeats customer-facing output/download value, so it could be tightened without losing meaning.

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?

For a read-only gradient generator with fully described parameters and an output schema, the description covers purpose, behavior, output forms, evidence-vs-final-palette distinction, and downstream registration with palette_finalize. No critical agent-facing gap remains.

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 the baseline is 3; the description still adds some semantic value by naming the CIEDE2000 snapping metric and explaining the visual consequence of chroma_preserved ('avoids desaturated midpoints'). Much of the remaining parameter meaning is duplicated from the schema rather than expanded.

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 opens with a specific verb and resource: 'Generate a perceptually smooth gradient between 2-5 archive anchor colours.' It also describes snapping, interpolation choices, output forms, and explicitly distinguishes archive anchors as evidence rather than recommended colours, while routing final registration to palette_finalize.

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?

It gives concrete use cases ('design briefs, colour journey visualisations, and gradient systems') and names palette_finalize as the downstream tool for a final palette chosen from this evidence. It also clarifies the conceptual boundary that anchor colours are evidence, not the recommendation itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources