Skip to main content
Glama

Specify Colour Palette for a Room

palette_specify
Read-only

Generate a complete interior specification from 2-8 hex values. Returns surface assignments, 60-30-10 proportions, lighting behaviour, and archive colour names. 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": {
      "colours": "<colours>"
    },
    "name": "palette_specify"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoe.g. 'heritage', 'contemporary', 'minimal'
coloursYesList of 2-8 hex values
room_typeNoe.g. 'living', 'bedroom', 'kitchen', 'study'

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      +}
  2. 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
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description is consistent with a pure generation step while adding real behavioural context: the result 'already carries the rendered palette and its PNG, PDF, ASE, JSON and CSS downloads', and the archive anchors 'are evidence, not the recommended colours'. The 'called once' workflow constraint is a useful behavioural caveat. It stops short of saying whether generated artifacts persist or are addressable afterwards.

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?

Four sentences, front-loaded with what is produced and followed by output contents, the evidence caveat, and the finalize hand-off. Nearly every sentence earns its place, though 'ready to show the customer' is scene-setting rather than operational detail.

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?

An output schema exists, yet the description still summarises what comes back (surface assignments, proportions, downloads) and clarifies the interpretive trap that archive anchor colours are evidence rather than recommendations. The sibling relationship to palette_finalize is resolved, so an agent has everything needed to call this correctly in the workflow.

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 all three parameters carry schema descriptions, so the baseline is 3. The description restates the 2-8 hex-value constraint on 'colours' but adds nothing about how 'style' or 'room_type' affect the output beyond what the schema examples already imply.

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 interior specification from 2-8 hex values') and enumerates the outputs (surface assignments, 60-30-10 proportions, lighting behaviour, archive colour names). It also separates itself from the nearest sibling by explaining that palette_finalize is what registers the chosen colours, so an agent can tell the two apart 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?

Gives clear workflow context: this tool produces evidence from 2-8 hex values, and the final palette selected from that evidence is registered with palette_finalize, called once with those exact colours. That names the alternative and the hand-off condition, but it does not state when NOT to use this tool (e.g. for analysis of an existing palette rather than generating a spec).

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