Skip to main content
Glama

Complete Brand Colour System

brand_system
Read-only

Complete brand colour system in one call. Returns colour roles with archive names, light and dark mode role maps, typography guidance, usage rules per colour, design tokens (CSS, Tailwind, Figma), and citation cards. Deterministic. No LLM cost. 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": {
      "palette": "<palette>"
    },
    "name": "brand_system"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketNoTarget market e.g. global, UK, Japanglobal
mediumNodigital | print | bothdigital
paletteYesHex values
use_caseNoUse case e.g. brand identity, packagingbrand identity
brand_categoryNoOptional e.g. developer tool, luxury, food
nature_palette_idNoOptional. A Nature Palette record_id (from archive_search or palette_concept). The brand is built from that palette's reviewed brand-identity translation, every colour labelled retained / interpreted / added, beside the unchanged scientific palette; palette may then be empty.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / nature_palette_id
      Added value: +{
      +  "description": "Optional. A Nature Palette record_id (from archive_search or palette_concept). The brand is built from that palette's reviewed brand-identity translation, every colour labelled retained / interpreted / added, beside the unchanged scientific palette; palette may then be empty.",
      +  "type": "string"
      +}
  2. 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"
      +}
  3. 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
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation by disclosing determinism ('Deterministic. No LLM cost.') and that the result self-contains rendered palette assets with PNG, PDF, ASE, JSON and CSS downloads. Critically, it prevents a likely misinterpretation by clarifying that archive anchors are derivation evidence rather than recommendations, and it sets the one-call contract for the palette_finalize handoff.

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?

Purpose and payload are front-loaded in the first sentence, and the workflow guidance follows logically. There is some repetition about the customer seeing and downloading the palette across two sentences, and the return-value enumeration is somewhat redundant against the output schema, but nothing is seriously off-topic.

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 multi-output tool, the description covers purpose, determinism, deliverable formats, the evidence-versus-recommendation distinction, and the downstream finalize handoff, with the output schema carrying return structure. An agent has everything needed to call it and to act on the result correctly.

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%, so all six parameters, including the nature_palette_id fallback where palette may be empty, are already documented in the schema. The description does not add format or constraint detail beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ('Complete brand colour system in one call') and enumerates exactly what it returns: colour roles with archive names, light/dark role maps, typography guidance, usage rules, design tokens and citation cards. It separates itself from palette_finalize by describing that tool as the downstream registration step, though it does not distinguish itself from adjacent siblings such as brand_report or brand_asset_pack.

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 is the evidence-gathering step, and the chosen palette is then registered with palette_finalize 'called once with those exact colours'. It also warns that archive anchors are evidence, not the recommended colours. It stops short of stating when NOT to call this (e.g. when a finalized palette already exists), but the sequencing guidance is explicit.

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