Skip to main content
Glama

Generate Palette PDF

palette_pdf
Read-only

Generate a premium branded PDF specification sheet from a palette of archive entries. Returns a downloadable PDF with full-bleed colour panels, archive names, provenance notes, RAL nearest match, LRV, chroma, WCAG contrast data, and Colour Memory branding. Use this to create client deliverables, specification sheets, and print assets. TRUST BOUNDARY: every colour rendered in this PDF 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 for that colour; an entry that matches no real archive record refuses the whole request (PDF_ENTRY_NOT_VERIFIED) rather than being dropped or rendered with the caller's claim. Two supported entry sources: (1) the flat entries array from query_hex or palette_from_concept -- each item needs name, hex, archive_source (colour_notes/primary_source/zone may be supplied but are ignored/overwritten by the server-verified record); or (2) archive_report_brief's output -- pass report['presented_cards'] as entries, NOT report['colour_cards'] (the legacy field is kept only for backward compatibility and does not carry family-card presentation). presented_cards may mix three card shapes, all rendered as exactly one page each regardless of how many underlying records they represent: single_cultivar (a normal flat card), colour_family (card_type='colour_family', many 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 carrying family_grouping_suppressed=true and also_supported_by, representing a larger natural family that was folded into one promoted cultivar instead of shown as a group). delivery controls how the PDF is returned: 'url' (default) gives a signed, time-limited R2 download link; 'base64' returns the PDF bytes inline in the response for callers that need the file directly rather than a link. This tool requires a valid, authenticated API key EXCEPT when using house_ref alone (anonymous house_ref access is unchanged) -- entries, sections, and project_id all require a key; a keyless request to those returns 401. No extra credit is charged for the key check itself. Alternative input mode: pass sections instead of entries for a grouped, multi-section document (e.g. house_specify's rooms) instead of one page per flat colour card. Each section has entries (verified exactly like the flat-entries path above) and, optionally, grouping_basis/hero_hex. DO NOT send title, subtitle, rationale, or application_notes on a section -- these are requester free text, and this renderer cannot currently keep them cleanly separated from Colour Memory's own evidence, so any of them being present REFUSES THE WHOLE REQUEST with a 400 (REQUESTER_FREE_TEXT_NOT_ALLOWED) naming the offending field(s); a section with only entries still renders, with an auto-numbered heading. presentation.template picks the layout: 'sectioned_specification' (clean grid-per-section spec sheet) or 'colour_drenched_lookbook' (hero colour fills the page, swatches cover most of it, citations collected into a final appendix rather than shrunk onto every page). Third input mode: pass house_ref (NOT house) -- the reference string house_specify's own response returns -- for the flagship document-plan pipeline: a complete, editorial multi-archetype publication with a cover, a house_thesis argument page, a whole_house_progression chart, one room_hero + one implementation (practical specification) page per room, and a redesigned source_appendix, all sharing one design system. house_ref (or project_id, for an authenticated caller's own durable project) is the ONLY way to reach this pipeline: passing the house_specify response object itself as an inline house field is REFUSED outright (400, INLINE_HOUSE_NOT_ALLOWED) -- this PDF is Colour Memory-branded, and it can only render a house Colour Memory itself created and still holds, never one relayed back through the request body, even unmodified. Call house_specify first, then pass the house_ref it returns here. house_ref/project_id takes priority over sections/entries when supplied.

Input Schema

TableJSON 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
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

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. 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"
      +}
  3. 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."
  4. 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."
  5. 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: +[]
  6. 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)."
  7. 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"
      +}
  8. 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
  9. 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."
  10. Added

TDQS

A4.7/5.0
Behavior5/5

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

The annotation only declares readOnlyHint=true, so the description carries the full disclosure burden — and it delivers comprehensively. It reveals the server-side verification boundary ('every colour rendered in this PDF is verified server-side against the real archive... any claim_strength, primary_source... is IGNORED'), the exact refusal codes (PDF_ENTRY_NOT_VERIFIED, REQUESTER_FREE_TEXT_NOT_ALLOWED, INLINE_HOUSE_NOT_ALLOWED), the auth requirement ('This tool requires a valid, authenticated API key EXCEPT when using house_ref alone'), the delivery mechanics (signed time-limited R2 link vs base64), and even the credit policy ('No extra credit is charged for the key check itself'). This goes far beyond what any annotation provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence carries substantive content — there is zero filler — but the description is a dense wall of text running many paragraphs with no visual segmentation (no bullets, no section breaks between the TRUST BOUNDARY, input modes, delivery, and auth discussions). The sheer length (well over 500 words) is partially justified by the tool's genuine complexity (three input modes, verification, multiple refusal paths, sibling-tool integration), yet an agent must parse critical rules like the REQUESTER_FREE_TEXT_NOT_ALLOWED refusal out of a continuous block. Front-loading is good (purpose first) but structure is not. This is appropriately sized for the complexity but poorly structured for efficient parsing.

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 tool with 10 parameters, nested objects, three input modes, server-side verification, and deep sibling-tool integration, the description is remarkably complete. It covers every input path (entries, sections, house_ref/project_id), the verification semantics with exact error codes, auth requirements and the keyless house_ref exception, delivery options, presentation template choices with defaults, versioning via project_version, and the priority rule. The output schema exists to document the return format, so no gap there. The only detail relegated to the schema (house_ref 30-minute validity) is properly placed in the parameter description. I cannot identify a significant omission for correct invocation.

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 the schema descriptions themselves are unusually rich (the `house` parameter alone explains the INLINE_HOUSE_NOT_ALLOWED refusal). The tool description adds genuine cross-parameter meaning the schema cannot: the three mutually exclusive input modes, the priority rule ('house_ref/project_id takes priority over sections/entries when supplied'), the verification flow tying entries to the archive, and the project_version semantics. The description synthesizes the parameters into a coherent workflow rather than repeating the schema — a clear value-add above the baseline 3 for full schema coverage.

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+resource+output: 'Generate a premium branded PDF specification sheet from a palette of archive entries. Returns a downloadable PDF with full-bleed colour panels, archive names, provenance notes, RAL nearest match, LRV, chroma, WCAG contrast data, and Colour Memory branding.' It names the use case ('client deliverables, specification sheets, print assets') and the output format, and its scope is clearly distinct from siblings like palette_export (a different export path) and brand_guideline_pdf (a different PDF). The opening sentence alone resolves what this tool is for.

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?

Exceptionally explicit. The description opens with the use case ('Use this to create client deliverables, specification sheets, and print assets'), then details all three input modes (entries, sections, house_ref/project_id) with exact routing rules: 'Call house_specify first, then pass the house_ref it returns here,' 'pass report['presented_cards'] as entries, NOT report['colour_cards'],' and explicit DO-NOTs ('DO NOT send title, subtitle, rationale, or application_notes on a section'). It even names the sibling tools whose output feeds this one, leaving no ambiguity about when to invoke it versus alternatives.

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