Skip to main content
Glama

Full Design Session: Concept to Complete Palette

design_session
Read-only

One-call compound tool. Submit a concept, medium, audience, and constraints; receive a complete design package: historically grounded palette, cultural narrative, commercial paint matches, WCAG accessibility check, illuminant behaviour, and a ready-made image generation prompt. Replaces chaining query_conceptual + palette_from_concept + colour_story + match_paint_system + accessibility_check + get_colour_metrics. Use when an AI agent or user needs a complete, deployable colour direction in a single call. Not for iterative refinement; use individual tools for that. 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": "design_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
avoidNoArchive names or colour terms to exclude e.g. ['neon', 'ScreenDigital']
mediumNoApplication context e.g. 'interior', 'brand identity', 'fashion', 'digital', 'print'general
conceptYesCultural theme, mood, or brief e.g. 'Victorian mourning', 'Ottoman court', 'Scandinavian minimal'
n_coloursNoPalette size (default 5, max 8)
include_promptNoInclude image generation prompt (default true)
include_accessibilityNoInclude WCAG contrast check (default true)
include_paint_matchesNoInclude commercial paint matches (default true)

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. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds the composite nature of the call, the download formats bundled in the result, and the caveat that archive anchors are evidence rather than recommendations. That caveat is genuinely useful context beyond the annotations. It stops short of disclosing cost, latency, or failure modes of a call that fans out to six subsystems.

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 the payload and the replaced chain, then the when/when-not, then the post-step guidance. It is longer than most definitions, but nearly every sentence carries routing or workflow information; the closing sentences about evidence-vs-recommendation are dense but earn their place.

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?

For a seven-parameter compound tool with an output schema, the description covers what is returned, in what artifacts, and what to do next. The only real gap is the inaccurate parameter gloss, which is scored under parameter semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description says the caller submits 'a concept, medium, audience, and constraints', but no audience parameter exists and 'constraints' only loosely maps to avoid. Schema coverage is 100%, so the schema already does the work; the description's parameter gloss misnames rather than enriches, risking an agent inventing an audience argument.

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 framing ('One-call compound tool') and enumerates exactly what the caller submits and receives (palette, narrative, paint matches, WCAG check, illuminant behaviour, image prompt). It also names the six sibling tools it replaces, so an agent can distinguish it from the individual building blocks without opening any 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?

States the trigger explicitly ('when an AI agent or user needs a complete, deployable colour direction in a single call') and the exclusion ('Not for iterative refinement; use individual tools for that'). It goes further and describes the follow-up step, naming palette_finalize and the exact condition for calling it.

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