Skip to main content
Glama

Interior Colour Specification: Full Room Brief

interior_specify
Read-only

Generate a complete interior colour specification from a concept or brief. Takes a room concept, type and style and returns a professionally structured colour scheme with 60/30/10 surface assignments, archive colour names with full cultural provenance, Farrow and Ball and Little Greene paint matches, three-illuminant light behaviour (D65 daylight, F11 atrium, Illuminant A incandescent), WCAG accessibility for digital use, and a written cultural rationale explaining why each colour belongs in this room. Examples: 'bold maximalist living room', 'calm Scandi bedroom', 'Victorian study', 'coastal kitchen', 'gallery hallway'. archive locks the whole scheme to one named archive (e.g. 'ArtsAndCrafts', 'GeorgianPleasures'): every returned colour belongs to it, or the response is a clear error listing valid archive names rather than a silent unrestricted search. A downloadable branded PDF version is available at /interior-specification/pdf. house_specify covers multi-room schemes with cross-room provenance grouping. This is the tool that replaces a colour consultation. When the concept names an animal with a Nature Palette that has a reviewed interior translation, the scheme is built from it and each colour states whether it keeps a measured value, interprets the catalogue's words or is a design addition. 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>"
    },
    "name": "interior_specify"
  }
}

Input Schema

NameRequiredDescriptionDefault
avoidNoColours, pigments or topics to exclude e.g. ['arsenic green']. Applied before selection.
styleNoStyle direction e.g. 'heritage', 'contemporary', 'maximalist', 'minimal', 'scandi', 'industrial', 'coastal'heritage
archiveNoOptional: restrict the candidate pool to this single archive before scoring, e.g. 'ArtsAndCrafts' or 'GeorgianPleasures'. Invalid names return a clear error listing valid archives rather than silently searching everything. Omit for unrestricted cross-archive search (default, unchanged behaviour).
conceptYesRoom concept or brief e.g. 'bold maximalist living room' or 'calm Scandi bedroom'
n_coloursNoNumber of colours in scheme (default 5, max 7)
role_planNoOptional: the room's spatial hierarchy, decided BEFORE colours are retrieved, so retrieval can be asked for candidates that suit a named job on a named surface. The role vocabulary is open -- field, architectural, ground, joinery, material, textile, accent and signal are all reasonable, and a room may need three of them or six. Omit to let the endpoint decide the hierarchy itself (unchanged behaviour).
room_typeNoRoom type e.g. 'living', 'bedroom', 'kitchen', 'study', 'bathroom', 'hallway', 'dining'living
orientationNoRoom orientation e.g. 'north', 'south', 'east', 'west' — affects light advice
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

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 / role_plan
      Added value: +{
      +  "default": [],
      +  "description": "Optional: the room's spatial hierarchy, decided BEFORE colours are retrieved, so retrieval can be asked for candidates that suit a named job on a named surface. The role vocabulary is open -- field, architectural, ground, joinery, material, textile, accent and signal are all reasonable, and a room may need three of them or six. Omit to let the endpoint decide the hierarchy itself (unchanged behaviour).",
      +  "items": {
      +    "properties": {
      +      "allow_contrast": {
      +        "default": false,
      +        "description": "Whether this role may contrast with the scheme rather than harmonise.",
      +        "type": "boolean"
      +      },
      +      "intent": {
      +        "default": "",
      +        "description": "What this role is for, in words.",
      +        "type": "string"
      +      },
      +      "proportion": {
      +        "description": "ONLY when the plan genuinely specifies one. An ungrounded percentage reads as a measured area split that nobody computed.",
      +        "type": "string"
      +      },
      +      "role": {
      +        "description": "The job this colour does in the room e.g. 'ground', 'joinery', 'accent'.",
      +        "type": "string"
      +      },
      +      "surfaces": {
      +        "default": [],
      +        "description": "Where it goes e.g. ['walls'], ['skirting', 'architrave'].",
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "target_hex": {
      +        "default": "",
      +        "description": "Approximately the colour the intent means, stated by you. A TARGET, not the answer -- the archive still supplies the real colour. Without it, 'a warm sunny yellow' is answered by text similarity over record names and can return a mauve sweet pea called Wendy's Joy.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "role"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / archive
      Added value: +{
      +  "default": "",
      +  "description": "Optional: restrict the candidate pool to this single archive before scoring, e.g. 'ArtsAndCrafts' or 'GeorgianPleasures'. Invalid names return a clear error listing valid archives rather than silently searching everything. Omit for unrestricted cross-archive search (default, unchanged behaviour).",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / avoid
      Added value: +{
      +  "default": [],
      +  "description": "Colours, pigments or topics to exclude e.g. ['arsenic green']. Applied before selection.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  5. 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"
      +}
  6. 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
  7. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond readOnlyHint=true, it discloses invalid-archive error behavior, provenance categories for reviewed Nature Palettes, and the rendered/downloadable artifacts. Clarifying that archive anchors are evidence rather than recommendations, and that registration happens separately through palette_finalize, materially helps the agent interpret and handle results.

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 definition is a dense single paragraph mixing output inventory, selection guidance, exceptional behavior and workflow. "This is the tool that replaces a colour consultation" is promotional, and the standalone PDF-path statement partly repeats the later download-artifact information.

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 complex nine-parameter tool, the overall definition is complete: the schema supplies invocation details and defaults, the output schema covers return structure, and the prose adds scope, errors, provenance interpretation and sibling handoffs. No further return-value explanation is necessary, and the described generation behavior is consistent with the read-only annotation.

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 coverage is 100%, so the baseline is 3 and the schema already documents all nine parameters, including detailed role_plan semantics. The additional concept examples and animal/Nature Palette trigger add some meaning, but the room concept/type/style and archive discussion mostly repeats structured field documentation.

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?

"Generate a complete interior colour specification" identifies a specific action and resource, then distinguishes the deliverable through surface assignments, provenance, paint matches, illuminant behaviour, accessibility and cultural rationale. The room examples and pointer to house_specify for multi-room schemes make its room-level scope and sibling boundary concrete.

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 supplies concrete brief examples, routes multi-room work to house_specify, and explains archive restriction and the special animal/Nature Palette case. It also gives an explicit downstream workflow: choose the final colours and call palette_finalize once with exactly those colours.

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