Skip to main content
Glama

Generate Palette PDF

palette_pdf
Read-only

Generates a premium branded PDF specification sheet from a palette of archive entries: full-bleed colour panels, archive names, provenance notes, RAL nearest match, LRV, chroma, WCAG contrast data and Colour Memory branding. Suited to client deliverables, specification sheets and print assets. TRUST BOUNDARY: every colour is verified server-side against the real archive by (name, hex, archive_source) before it is drawn. Any claim_strength, primary_source, colour_notes, colour_basis or hex_confidence supplied in entries/sections is ignored and replaced with Colour Memory's own record; an entry that matches no archive record refuses the whole request (PDF_ENTRY_NOT_VERIFIED) rather than being dropped or rendered with the caller's claim. Entry sources: (1) the flat entries array from query_hex or palette_from_concept, each item with name, hex, archive_source (colour_notes/primary_source/zone are accepted but overwritten by the verified record); or (2) archive_report_brief's output, where report['presented_cards'] is the entries list (report['colour_cards'] is a legacy field without family-card presentation). presented_cards may mix three card shapes, each rendered as exactly one page however many records it represents: single_cultivar (a normal flat card), colour_family (card_type='colour_family': near-identical records summarised as one card with member_count/supported_by/family_delta_e_max; every member is verified individually and representative_hex must be one of the verified members' own hexes), and conservative-mode hero cards (a single_cultivar card with family_grouping_suppressed=true and also_supported_by, standing for a larger family folded into one promoted cultivar). delivery: 'url' (default) returns a signed, time-limited R2 download link; 'base64' returns the PDF bytes inline. A valid, authenticated API key is required for entries, sections and project_id (a keyless request returns 401); house_ref alone works without a key. The key check costs no extra credit. Second input mode: sections instead of entries gives a grouped, multi-section document (e.g. house_specify's rooms). Each section has entries (verified as above) and optional grouping_basis/hero_hex. Sections accept no title, subtitle, rationale or application_notes: these are requester free text that this renderer cannot yet keep separate from Colour Memory's evidence, so any of them refuses the whole request with a 400 (REQUESTER_FREE_TEXT_NOT_ALLOWED) naming the field(s); a section with only entries renders with an auto-numbered heading. presentation.template: 'sectioned_specification' (grid-per-section spec sheet) or 'colour_drenched_lookbook' (hero colour fills the page, citations collected in a final appendix). Third input mode: house_ref (not house), the reference string house_specify returns, reaches the flagship document-plan pipeline: an editorial multi-archetype publication with a cover, a house_thesis page, a whole_house_progression chart, a room_hero and an implementation page per room, and a source_appendix, in one design system. house_ref (or project_id, for an authenticated caller's own durable project) is the only way in: an inline house object is refused (400, INLINE_HOUSE_NOT_ALLOWED), because this Colour Memory-branded PDF renders only a house Colour Memory itself created and still holds, never one relayed back through the request body. house_ref/project_id takes priority over sections/entries.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "palette_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
houseNoDO NOT USE. Inline house objects are REFUSED outright (400, INLINE_HOUSE_NOT_ALLOWED), even alongside a valid house_ref/project_id -- this PDF is Colour Memory-branded and can only render a house Colour Memory itself created and still holds, never one relayed back through the request body. Call house_specify, then pass the house_ref it returns in `house_ref` below instead.
queryNoOptional title for the palette e.g. Ottoman imperial luxury
sourceNoOptional source label e.g. brand, conceptualarchive
verifyNoIssue as a Verified by Colour Memory document (Colour Memory Pro).
entriesNoArray of colour cards. Either the flat entries array from query_hex/palette_concept, or report['presented_cards'] from archive_report_brief (single_cultivar, colour_family, and conservative-mode hero cards are all supported -- see tool description). Omit if using `sections` instead. EVIDENCE FIELDS ARE SERVER-VERIFIED: each entry's name+hex(+archive_source) must match a real archive record -- any claim_strength/primary_source/colour_notes/colour_basis/hex_confidence supplied here is ignored and replaced with Colour Memory's own record; a non-matching entry refuses the whole request. Requires a valid API key.
deliveryNo'url' (default): signed, time-limited R2 download link. 'base64': PDF bytes returned inline as pdf_base64 for callers that need the file directly.
sectionsNoAlternative to `entries` -- one entry per document section, e.g. house_specify's rooms. Each: {grouping_basis?, hero_hex?, entries: [...colour cards, server-verified exactly like the flat `entries` field above...]}. DO NOT include title/subtitle/rationale/application_notes -- this renderer cannot currently keep that requester free text cleanly separated from Colour Memory's own evidence, so any of them present REFUSES THE WHOLE REQUEST with 400 REQUESTER_FREE_TEXT_NOT_ALLOWED naming the field(s); a section with only `entries` still renders, with an auto-numbered heading. Requires a valid API key.
house_refNoTHE way to render the flagship document-plan publication -- the house_ref string house_specify's own response returns (valid for 30 minutes after that call, or per project_persistence for a durable/temporary project). Renders the identical flagship document without resending the house object over the wire, and without it ever being treated as caller-supplied evidence. Anonymous house_ref access needs no API key, unchanged; do not send `house` alongside it.
project_idNoAlternative to house_ref for an authenticated (keyed) caller's own durable project -- the project_id house_specify returned. Requires the same API key that created the project.
presentationNoUsed with `sections` or `house_ref`/`project_id`. {template: 'sectioned_specification'|'colour_drenched_lookbook' (sections only), page_size?: 'A4-portrait'|'A4-landscape'|'16:9', minimum_colour_coverage?: number (default 0.55 for lookbook), source_display?: 'inline'|'appendix', max_body_words_per_page?: integer, min_body_font_pt?: number (default 10.5), min_label_font_pt?: number (default 9, swatch colour-name labels), min_citation_font_pt?: number (default 7.5, appendix citations and page furniture)}. No rendered text falls below its category's floor -- names that don't fit are truncated with an ellipsis, never shrunk past the floor.
project_versionNoUsed with either house_ref or project_id -- render this specific immutable version instead of the project's current version. Omit to render the current version.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / verify
      Added value: +{
      +  "description": "Issue as a Verified by Colour Memory document (Colour Memory Pro).",
      +  "type": "boolean"
      +}
  2. Changed5 schema fields changed
    • changedInput schema / properties / entries / description
      Previous value: -"Array of colour cards. Either the flat entries array from query_hex/palette_concept, or report['presented_cards'] from archive_report_brief (single_cultivar, colour_family, and conservative-mode hero cards are all supported -- see tool description). Omit if using `sections` instead."New value: +"Array of colour cards. Either the flat entries array from query_hex/palette_concept, or report['presented_cards'] from archive_report_brief (single_cultivar, colour_family, and conservative-mode hero cards are all supported -- see tool description). Omit if using `sections` instead. EVIDENCE FIELDS ARE SERVER-VERIFIED: each entry's name+hex(+archive_source) must match a real archive record -- any claim_strength/primary_source/colour_notes/colour_basis/hex_confidence supplied here is ignored and replaced with Colour Memory's own record; a non-matching entry refuses the whole request. Requires a valid API key."
    • changedInput schema / properties / house / description
      Previous value: -"Alternative to `entries`/`sections` -- pass house_specify's full response object unmodified (house_title, house_thesis, progression, shared_house_palette, rooms) to render the complete flagship document-plan publication instead of a flat or sectioned layout. PREFER `house_ref` instead when available -- a real house response is easily 60-100KB+, which can be rejected before it reaches this API; house_ref avoids sending it at all."New value: +"DO NOT USE. Inline house objects are REFUSED outright (400, INLINE_HOUSE_NOT_ALLOWED), even alongside a valid house_ref/project_id -- this PDF is Colour Memory-branded and can only render a house Colour Memory itself created and still holds, never one relayed back through the request body. Call house_specify, then pass the house_ref it returns in `house_ref` below instead."
    • changedInput schema / properties / house_ref / description
      Previous value: -"Preferred alternative to `house` -- the house_ref string house_specify returns in its own response (valid for 30 minutes after that call, or per project_persistence for a durable/temporary project). Renders the identical flagship document without resending the (often large) house object over the wire."New value: +"THE way to render the flagship document-plan publication -- the house_ref string house_specify's own response returns (valid for 30 minutes after that call, or per project_persistence for a durable/temporary project). Renders the identical flagship document without resending the house object over the wire, and without it ever being treated as caller-supplied evidence. Anonymous house_ref access needs no API key, unchanged; do not send `house` alongside it."
    • changedInput schema / properties / presentation / description
      Previous value: -"Used with `sections` or `house`. {template: 'sectioned_specification'|'colour_drenched_lookbook' (sections only), page_size?: 'A4-portrait'|'A4-landscape'|'16:9', minimum_colour_coverage?: number (default 0.55 for lookbook), source_display?: 'inline'|'appendix', max_body_words_per_page?: integer, min_body_font_pt?: number (default 10.5, rationale/application-note body text), min_label_font_pt?: number (default 9, swatch colour-name labels), min_citation_font_pt?: number (default 7.5, appendix citations and page furniture)}. No rendered text falls below its category's floor -- names that don't fit are truncated with an ellipsis, never shrunk past the floor."New value: +"Used with `sections` or `house_ref`/`project_id`. {template: 'sectioned_specification'|'colour_drenched_lookbook' (sections only), page_size?: 'A4-portrait'|'A4-landscape'|'16:9', minimum_colour_coverage?: number (default 0.55 for lookbook), source_display?: 'inline'|'appendix', max_body_words_per_page?: integer, min_body_font_pt?: number (default 10.5), min_label_font_pt?: number (default 9, swatch colour-name labels), min_citation_font_pt?: number (default 7.5, appendix citations and page furniture)}. No rendered text falls below its category's floor -- names that don't fit are truncated with an ellipsis, never shrunk past the floor."
    • changedInput schema / properties / sections / description
      Previous value: -"Alternative to `entries` -- one entry per document section, e.g. house_specify's rooms. Each: {title, subtitle?, rationale, grouping_basis?, hero_hex?, entries: [...colour cards...], application_notes?: [{surface, colour_name, instruction}]}."New value: +"Alternative to `entries` -- one entry per document section, e.g. house_specify's rooms. Each: {grouping_basis?, hero_hex?, entries: [...colour cards, server-verified exactly like the flat `entries` field above...]}. DO NOT include title/subtitle/rationale/application_notes -- this renderer cannot currently keep that requester free text cleanly separated from Colour Memory's own evidence, so any of them present REFUSES THE WHOLE REQUEST with 400 REQUESTER_FREE_TEXT_NOT_ALLOWED naming the field(s); a section with only `entries` still renders, with an auto-numbered heading. Requires a valid API key."
  3. Changed3 schema fields changed
    • changedInput schema / properties / house_ref / description
      Previous value: -"Preferred alternative to `house` -- the house_ref string house_specify returns in its own response (valid for 30 minutes after that call). Renders the identical flagship document without resending the (often large) house object over the wire."New value: +"Preferred alternative to `house` -- the house_ref string house_specify returns in its own response (valid for 30 minutes after that call, or per project_persistence for a durable/temporary project). Renders the identical flagship document without resending the (often large) house object over the wire."
    • addedInput schema / properties / project_id
      Added value: +{
      +  "description": "Alternative to house_ref for an authenticated (keyed) caller's own durable project -- the project_id house_specify returned. Requires the same API key that created the project.",
      +  "type": "string"
      +}
    • addedInput schema / properties / project_version
      Added value: +{
      +  "description": "Used with either house_ref or project_id -- render this specific immutable version instead of the project's current version. Omit to render the current version.",
      +  "type": "integer"
      +}
  4. Changed3 schema fields changed
    • addedInput schema / properties / house
      Added value: +{
      +  "description": "Alternative to `entries`/`sections` -- pass house_specify's full response object unmodified (house_title, house_thesis, progression, shared_house_palette, rooms) to render the complete flagship document-plan publication instead of a flat or sectioned layout. PREFER `house_ref` instead when available -- a real house response is easily 60-100KB+, which can be rejected before it reaches this API; house_ref avoids sending it at all.",
      +  "type": "object"
      +}
    • addedInput schema / properties / house_ref
      Added value: +{
      +  "description": "Preferred alternative to `house` -- the house_ref string house_specify returns in its own response (valid for 30 minutes after that call). Renders the identical flagship document without resending the (often large) house object over the wire.",
      +  "type": "string"
      +}
    • changedInput schema / properties / presentation / description
      Previous value: -"Only used with `sections`. {template: 'sectioned_specification'|'colour_drenched_lookbook', page_size?: 'A4-portrait'|'A4-landscape'|'16:9', minimum_colour_coverage?: number (default 0.55 for lookbook), source_display?: 'inline'|'appendix', max_body_words_per_page?: integer, min_body_font_pt?: number (default 10.5, rationale/application-note body text), min_label_font_pt?: number (default 9, swatch colour-name labels), min_citation_font_pt?: number (default 7.5, appendix citations and page furniture)}. No rendered text falls below its category's floor -- names that don't fit are truncated with an ellipsis, never shrunk past the floor."New value: +"Used with `sections` or `house`. {template: 'sectioned_specification'|'colour_drenched_lookbook' (sections only), page_size?: 'A4-portrait'|'A4-landscape'|'16:9', minimum_colour_coverage?: number (default 0.55 for lookbook), source_display?: 'inline'|'appendix', max_body_words_per_page?: integer, min_body_font_pt?: number (default 10.5, rationale/application-note body text), min_label_font_pt?: number (default 9, swatch colour-name labels), min_citation_font_pt?: number (default 7.5, appendix citations and page furniture)}. No rendered text falls below its category's floor -- names that don't fit are truncated with an ellipsis, never shrunk past the floor."
  5. Changed1 schema field changed
    • changedInput schema / properties / presentation / description
      Previous value: -"Only used with `sections`. {template: 'sectioned_specification'|'colour_drenched_lookbook', page_size?: 'A4-portrait'|'A4-landscape'|'16:9', minimum_colour_coverage?: number (default 0.55 for lookbook), source_display?: 'inline'|'appendix', max_body_words_per_page?: integer, min_body_font_pt?: number}."New value: +"Only used with `sections`. {template: 'sectioned_specification'|'colour_drenched_lookbook', page_size?: 'A4-portrait'|'A4-landscape'|'16:9', minimum_colour_coverage?: number (default 0.55 for lookbook), source_display?: 'inline'|'appendix', max_body_words_per_page?: integer, min_body_font_pt?: number (default 10.5, rationale/application-note body text), min_label_font_pt?: number (default 9, swatch colour-name labels), min_citation_font_pt?: number (default 7.5, appendix citations and page furniture)}. No rendered text falls below its category's floor -- names that don't fit are truncated with an ellipsis, never shrunk past the floor."
  6. Changed4 schema fields changed
    • changedInput schema / properties / entries / description
      Previous value: -"Array of colour cards. Either the flat entries array from query_hex/palette_concept, or report['presented_cards'] from archive_report_brief (single_cultivar, colour_family, and conservative-mode hero cards are all supported -- see tool description)."New value: +"Array of colour cards. Either the flat entries array from query_hex/palette_concept, or report['presented_cards'] from archive_report_brief (single_cultivar, colour_family, and conservative-mode hero cards are all supported -- see tool description). Omit if using `sections` instead."
    • addedInput schema / properties / presentation
      Added value: +{
      +  "description": "Only used with `sections`. {template: 'sectioned_specification'|'colour_drenched_lookbook', page_size?: 'A4-portrait'|'A4-landscape'|'16:9', minimum_colour_coverage?: number (default 0.55 for lookbook), source_display?: 'inline'|'appendix', max_body_words_per_page?: integer, min_body_font_pt?: number}.",
      +  "type": "object"
      +}
    • addedInput schema / properties / sections
      Added value: +{
      +  "description": "Alternative to `entries` -- one entry per document section, e.g. house_specify's rooms. Each: {title, subtitle?, rationale, grouping_basis?, hero_hex?, entries: [...colour cards...], application_notes?: [{surface, colour_name, instruction}]}.",
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "entries"
      -]New value: +[]
  7. Changed2 schema fields changed
    • addedInput schema / properties / delivery
      Added value: +{
      +  "description": "'url' (default): signed, time-limited R2 download link. 'base64': PDF bytes returned inline as pdf_base64 for callers that need the file directly.",
      +  "enum": [
      +    "url",
      +    "base64"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / entries / description
      Previous value: -"Array of colour entries from query_hex or palette_concept. Each needs name, hex, archive_source, colour_notes, primary_source, zone."New value: +"Array of colour cards. Either the flat entries array from query_hex/palette_concept, or report['presented_cards'] from archive_report_brief (single_cultivar, colour_family, and conservative-mode hero cards are all supported -- see tool description)."
  8. 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"
      +}
  9. 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
  10. Changed1 schema field changed
    • changedInput schema / properties / entries / description
      Previous value: -"Array of colour entries from query_hex or palette_from_concept. Each needs name, hex, archive_source, colour_notes, primary_source, zone."New value: +"Array of colour entries from query_hex or palette_concept. Each needs name, hex, archive_source, colour_notes, primary_source, zone."
  11. Added

TDQS

A4.6/5.0
Behavior5/5

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

Despite readOnlyHint already signaling a safe read, the description discloses server-side verification, overwritten caller claims, refusal codes, auth behavior, signed URL delivery, and priority rules. This is rich behavioral context well beyond annotations.

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 description is front-loaded and organized under explicit labels (TRUST BOUNDARY, Entry sources, input modes). It is long and partially duplicates schema details, but the length is largely justified by three distinct input modes and strict verification rules.

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?

Covers all three input modes, auth, verification, error handling, delivery, and presentation options; with an output schema present, return value detail is unnecessary. Nothing material for correct invocation is missing.

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% and already documents each parameter in detail, so baseline is 3. The description adds cross-parameter semantics: house_ref/project_id overrides entries/sections, sections reject free-text fields, and card shapes map to pages, which helps an agent assemble a valid request.

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 ('Generates') and resource ('premium branded PDF specification sheet') and clearly scopes its three input modes and their sources (query_hex, archive_report_brief, house_specify). An agent can identify the output and required inputs 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?

Provides detailed conditions for each input mode and explicit refusal cases (inline house, requester free text), plus auth requirements for keyed vs keyless requests. It does not compare against sibling tools like palette_export or brand_guideline_pdf to say when this PDF renderer is preferred over those alternatives, leaving that inference to the agent.

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