Skip to main content
Glama

Multi-Room House Colour Scheme: Provenance-Grouped Where Documented

house_specify
Read-only

Generate a complete multi-room house colour scheme from a single archive. Where the retrieved evidence supports it, rooms are grouped by documented provenance (same object, same pattern colourway, same source citation, same designer, same period+institution); where it does not, they are grouped by perceptual similarity and the response says so -- grouping_basis reports which, and provenance_credit reports how many delivered colours are individually evidenced versus documented as a GROUP (often zero). Every colour is a real archive record either way. Each room gets a full colour card set (dominant/secondary/joinery/textile/accent roles) with paint matches, LRV, illuminant behaviour, and WCAG data. A documentary grouping states exactly which documented fact ties its colours together (e.g. 'documented on the same Fitzwilliam Museum record for the Artichoke hanging, accession T.1-1979') and its weighted grouping_strength score -- historical claims are templated only from fields the archive record actually states; room/surface assignment is disclosed as editorial, never as historical fact. Orientation (north/south/east/west) is recorded as room context and surfaced in each room's light_context; in the current model it does not alter palette selection. Example: concept='Arts and Crafts movement family house', archive='ArtsAndCrafts', rooms=[{label:'Entrance Hall', room_type:'hallway', orientation:'north'}, {label:'Living Room', room_type:'living', orientation:'south'}]. Use interior_specify instead for a single room without cross-room grouping. The response includes house_ref -- pass that (not the full response) to palette_pdf's house_ref input to render the flagship document; the full response is often 60-100KB+, too large to safely resend as another tool call's input. 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": {
      "concept": "<concept>",
      "archive": "<archive>",
      "rooms": "<rooms>"
    },
    "name": "house_specify"
  }
}

Input Schema

NameRequiredDescriptionDefault
avoidNoTerms to exclude from retrieval.
roomsYesOne entry per room, e.g. [{label:'Entrance Hall', room_type:'hallway', orientation:'north'}]
archiveYesSingle archive to draw every room's colours from, e.g. 'ArtsAndCrafts'. Required -- invalid names return a clear error listing valid archives.
conceptYesHouse-level concept or brief, e.g. 'Arts and Crafts movement family house'
output_formatNo'scene_brief' adds a Historical Scene Colour Brief for film and image work: per colour its place, date, observer, timing, source and do-not-claim lines, then DOCUMENTED VISUAL CONSTRAINTS, NEGATIVE / DO-NOT-INVENT constraints and a CREATIVE RECONSTRUCTION BOUNDARY. Evidence only; nothing is invented.standard
guidance_levelNoWho the guidance notes are written for. 'client' (default) for a homeowner; 'decorator' for a trade reader. The specification decisions are identical either way -- only the wording differs.client
narrative_modeNoDefault 'evidence_only'.evidence_only
colours_per_roomNoDefault 5.
shared_house_coloursNoDefault 2.
minimum_claim_strengthNoEvidence-grade floor, default 'B'. Explicitly supplied: a hard admission filter, never relaxed -- too few qualifying records fails closed with a per-grade availability map (ARCHIVE_EVIDENCE_POOL_DEPLETED). Left at the implicit default: if the archive's best relevant records sit below it, the design-admissibility floor is relaxed to the archive's best achievable grade and disclosed in the response's evidence_floor block. Colours always keep their true evidence grade either way -- claims are never upgraded.B
strict_semantic_colourNoDefault true -- excludes entries whose quoted colour language contradicts their stored hex.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / output_format
      Added value: +{
      +  "default": "standard",
      +  "description": "'scene_brief' adds a Historical Scene Colour Brief for film and image work: per colour its place, date, observer, timing, source and do-not-claim lines, then DOCUMENTED VISUAL CONSTRAINTS, NEGATIVE / DO-NOT-INVENT constraints and a CREATIVE RECONSTRUCTION BOUNDARY. Evidence only; nothing is invented.",
      +  "enum": [
      +    "standard",
      +    "scene_brief"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / guidance_level
      Added value: +{
      +  "default": "client",
      +  "description": "Who the guidance notes are written for. 'client' (default) for a homeowner; 'decorator' for a trade reader. The specification decisions are identical either way -- only the wording differs.",
      +  "enum": [
      +    "client",
      +    "decorator"
      +  ],
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / minimum_claim_strength / description
      Previous value: -"Evidence-grade floor, default 'B'."New value: +"Evidence-grade floor, default 'B'. Explicitly supplied: a hard admission filter, never relaxed -- too few qualifying records fails closed with a per-grade availability map (ARCHIVE_EVIDENCE_POOL_DEPLETED). Left at the implicit default: if the archive's best relevant records sit below it, the design-admissibility floor is relaxed to the archive's best achievable grade and disclosed in the response's evidence_floor block. Colours always keep their true evidence grade either way -- claims are never upgraded."
  4. Changed1 schema field changed
    • changedInput schema / properties / rooms / items / properties / orientation / description
      Previous value: -"Constrains candidate selection for this room, not just narration."New value: +"Optional room orientation. Recorded as descriptive light context and surfaced in light_context; it does not alter candidate selection."
  5. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the burden and does it well: it discloses that grouping_basis reports provenance vs perceptual grouping, that provenance_credit may often be zero, that room/surface assignment is editorial and never historical fact, that orientation does not alter palette selection, and that responses are 60-100KB+ and unsafe to resend whole. It also documents the fail-closed minimum_claim_strength behaviour and the confirmation that claims are never upgraded.

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?

The purpose is front-loaded, but the body is a single dense block that mixes grouping mechanics, provenance disclosure, downstream tool chaining, and output inventory. Some sentences restate each other ('Every colour is a real archive record either way' vs 'archive anchors ... are evidence, not the recommended colours'), and the PNG/PDF/ASE/CSS inventory largely duplicates what the output schema already conveys.

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 an 11-parameter generative tool with a thin annotation set, the description covers the failure modes (ARCHIVE_EVIDENCE_POOL_DEPLETED, evidence_floor relaxation), the disclosure contract, and how to chain into palette_pdf and palette_finalize. An output schema exists, so the description need not explain return values, and its remaining coverage is sufficient for correct invocation.

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 description coverage is 100% and the schema already documents avoid, rooms, archive, output_format, guidance_level, colours_per_room, minimum_claim_strength and strict_semantic_colour in detail. The description reinforces the archive constraint and gives a worked concept/archive/rooms example, but adds little field-level meaning beyond what the schema states. Baseline 3 applies.

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?

Opens with a specific verb and resource ('Generate a complete multi-room house colour scheme from a single archive') and immediately distinguishes itself from interior_specify by scope ('single room without cross-room grouping'). The agent can tell what it produces and how it differs from the nearest sibling 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 Guidelines5/5

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

Explicitly routes the single-room case to interior_specify and names the condition that selects it. It also states the downstream workflow: pass house_ref (not the full response) to palette_pdf, and register the final chosen palette with palette_finalize once. That is when-to-use plus when-to-use-something-else, with no inference required.

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