Skip to main content
Glama

Finalise a chosen palette

palette_finalize
Read-only

Packages an already-chosen palette into a professional, visible, downloadable deliverable. Takes the final colours once they have been decided, verifies and packages that decision, and returns the palette image plus PNG, SVG, PDF, ASE, JSON and CSS. It does not search, select, replace or improve anything: the colours sent are the colours that come back, in the same order. Each final colour is sent with its name; a colour is marked source-backed only when it is a Colour Memory archive record, and anything unverified is presented as the caller's recommendation, which is the honest description of it.

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_finalize"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefNoThe customer's request, in their words.
notesNoShort usage guidance, in your words.
titleNoWhat you are calling this palette.
coloursYesThe final palette, in the order you want it shown.
design_contextNoWith nature_palette_id: interior (default), brand identity, textile or packaging -- which reviewed translation to use.
source_anchorsNoArchive records that informed the palette but are not in it. Give the record's name so it can be verified.
nature_palette_idNoOptional. A Nature Palette record_id: the deliverable is built from that palette's reviewed design translation (send colours empty to use it as is), each colour labelled retained / adjusted / interpreted / added, with the scientific palette alongside. Only a retained measured colour of that palette is ever source-backed.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / design_context
      Added value: +{
      +  "description": "With nature_palette_id: interior (default), brand identity, textile or packaging -- which reviewed translation to use.",
      +  "type": "string"
      +}
    • addedInput schema / properties / nature_palette_id
      Added value: +{
      +  "description": "Optional. A Nature Palette record_id: the deliverable is built from that palette's reviewed design translation (send colours empty to use it as is), each colour labelled retained / adjusted / interpreted / added, with the scientific palette alongside. Only a retained measured colour of that palette is ever source-backed.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, so the description's job is added nuance, and it delivers: 'the colours sent are the colours that come back, in the same order' rules out silent reordering or correction, and it discloses that a claimed SOURCE-BACKED status is verified and downgraded, with unverified colours presented as the caller's recommendation. It does not say where the downloadable artifacts land or whether anything is persisted server-side, which is the remaining behavioural gap.

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 the core action and output formats in the first two sentences, then the no-transformation guarantee, then the provenance nuance. The closing clause ('which is the honest description of it') is editorial padding that could be cut, but the rest is dense and earns its place.

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, return values need not be detailed, yet the description still summarises the artifact set and the provenance-labelling rules that materially affect how the caller should populate status and source_anchors. The one unaddressed complexity is the nature_palette_id path (what happens on an unknown record_id) and the meaning of 'downloadable', which is left vague for a tool whose selling point is deliverables.

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 earns above that by explaining the consequence of the status field (a source-backed claim is checked and can be downgraded) and by clarifying that each colour travels with its name. It reinforces rather than repeats the nature_palette_id 'send colours empty to use it as is' semantics, and adds nothing on proportion or design_context beyond the 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?

Names a specific verb and resource ('packages an already-chosen palette into a deliverable') and enumerates the concrete artifacts returned (image, PNG, SVG, PDF, ASE, JSON, CSS). It explicitly distinguishes itself from selection/generation siblings by stating it 'does not search, select, replace or improve anything', so an agent can tell it apart from palette_generate or palette_export without opening either 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?

Timing is unambiguous: 'takes the final colours once they have been decided', i.e. use it at the end of the workflow, and the negative clause rules out using it for search/selection/improvement. It stops short of naming which sibling to use instead when colours are not yet decided (e.g. palette_generate or palette_iterate), so the alternative is implied rather than routed.

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