Skip to main content
Glama

Read-only

Displays a finished colour result to the customer as colour. Presents a palette, house scheme, brand system or audit that has already been decided; it chooses nothing. It is not designed for a single contrast figure, a colour history question with no palette, or tool guidance. Accepts a short story with it: one sentence on what the scheme is, the design decision behind it, and the one rule worth remembering. The colours cannot carry those on their own.

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": "render_colour_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNopalette, house, brand or audit.
roomsNoFor a multi-room scheme: one short line per room, in your own words. What that room is doing with the palette.
titleNoWhat this result is, in the customer's terms.
bridgeNoWhere the evidence started and where you took it. Include `colours` on a side ONLY if you have real colour values for it -- an invented source swatch beside a real archive one reads as evidence and is not.
checksNo
coloursYesThe colours you are handing over, in order.
verdictNoOne sentence, shown under the colour.
key_ruleNoThe one rule worth remembering, short enough to repeat to a decorator. 'Boathouse Clay stays tiny. Never a wall.'
design_moveNoAt most two sentences on the decision you made -- what the evidence offered and what you did with it. This is usually the most interesting thing in your answer and the part a list of colours cannot carry.
proportionsNoOnly where a real share was decided. Every colour gets one and they total 100, or leave this out entirely -- a share nobody decided reads as a measurement nobody took.
story_thesisNoONE sentence: what this scheme IS. 'Danish coastal colour, domesticated for a summer house.' Shown above the palette, so it must earn its line.
evidence_threadNoThree to five short sources or references that shaped this. Orientation, not a bibliography.
evidence_summaryNo
evidence_boundaryNoWhat is source-backed and what is your interpretation. Say it plainly: 'Designed contemporary interpretation, not a measured historical paint specification.'

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / bridge
      Added value: +{
      +  "description": "Where the evidence started and where you took it. Include `colours` on a side ONLY if you have real colour values for it -- an invented source swatch beside a real archive one reads as evidence and is not.",
      +  "properties": {
      +    "from": {
      +      "properties": {
      +        "colours": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "label": {
      +          "type": "string"
      +        },
      +        "note": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "to": {
      +      "properties": {
      +        "colours": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "label": {
      +          "type": "string"
      +        },
      +        "note": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / design_move
      Added value: +{
      +  "description": "At most two sentences on the decision you made -- what the evidence offered and what you did with it. This is usually the most interesting thing in your answer and the part a list of colours cannot carry.",
      +  "type": "string"
      +}
    • addedInput schema / properties / evidence_boundary
      Added value: +{
      +  "description": "What is source-backed and what is your interpretation. Say it plainly: 'Designed contemporary interpretation, not a measured historical paint specification.'",
      +  "type": "string"
      +}
    • addedInput schema / properties / evidence_thread
      Added value: +{
      +  "description": "Three to five short sources or references that shaped this. Orientation, not a bibliography.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / key_rule
      Added value: +{
      +  "description": "The one rule worth remembering, short enough to repeat to a decorator. 'Boathouse Clay stays tiny. Never a wall.'",
      +  "type": "string"
      +}
    • addedInput schema / properties / rooms
      Added value: +{
      +  "description": "For a multi-room scheme: one short line per room, in your own words. What that room is doing with the palette.",
      +  "items": {
      +    "properties": {
      +      "label": {
      +        "type": "string"
      +      },
      +      "summary": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "label"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / story_thesis
      Added value: +{
      +  "description": "ONE sentence: what this scheme IS. 'Danish coastal colour, domesticated for a summer house.' Shown above the palette, so it must earn its line.",
      +  "type": "string"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating render step, and 'it chooses nothing' is consistent with that. The description adds a useful editorial constraint (the story must accompany the palette because 'the colours cannot carry those on their own') but says nothing about rendering behavior, ordering, or what happens when optional sections are omitted.

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?

Front-loaded with purpose, then exclusions, then the narrative requirement — a sensible order with no filler sentences. The closing 'The colours cannot carry those on their own' earns its place as the rationale for the story, though the paragraph runs slightly long for a display tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and 86% parameter coverage, the description needn't explain return values and doesn't try. It covers what the tool does, what it refuses, and the narrative expectation; the heavier structured inputs (bridge integrity, proportions summing to 100) are carried by the schema's own warnings, so nothing critical is missing.

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 86%, so the schema already explains most of the 14 parameters. The description's story guidance ('one sentence on what the scheme is, the design decision behind it, and the one rule worth remembering') maps onto story_thesis, design_move and key_rule, which the schema already documents — it reinforces rather than adds. Bridge, proportions, rooms and evidence fields get no mention in the description.

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 and resource ('Displays a finished colour result ... as colour') and immediately scopes it: 'Presents a palette, house scheme, brand system or audit that has already been decided; it chooses nothing.' That framing separates it from generative siblings like colour_strategy or colour_story without needing their schemas.

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 when-not routing: 'not designed for a single contrast figure, a colour history question with no palette, or tool guidance' — which rules out colour_verdict, historical_colour_query and agent_brief style calls. It stops short of naming the alternative tools explicitly, so an agent must map the exclusions to siblings itself.

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