Skip to main content
Glama

Full Design Session — Concept to Complete Palette

design_session
Read-only

Receive a complete colour design package in a single call: provide concept, medium, audience, and constraints to receive palette, cultural narrative, paint matches, accessibility check, illuminant behaviour, and image prompt.

Instructions

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.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
resultNo
errorNo
Behavior4/5

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

Annotations declare readOnlyHint=true, consistent with reading/generating content. The description adds behavioral context by listing the components of the output package (palette, narrative, matches, etc.) and noting it's a one-call compound tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with three sentences, front-loaded with purpose, and contains no unnecessary words. Every sentence adds value.

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?

Given the tool's complexity (compound, 7 parameters, output schema exists), the description is complete: explains purpose, usage, and outputs. The presence of an output schema means return values are covered.

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 each parameter already has a description. The description adds high-level context but does not significantly expand on parameter meanings beyond what the schema provides.

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?

The description clearly states the tool as a compound tool that takes a concept, medium, audience, and constraints to produce a complete design package. It distinguishes itself from siblings by explicitly replacing chaining of multiple individual tools.

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?

Explicitly states when to use: 'Use when an AI agent or user needs a complete, deployable colour direction in a single call.' And when not: 'Not for iterative refinement — use individual tools for that.' Provides clear context and alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DigbyO/colour-memory-api'

If you have feedback or need assistance with the MCP directory API, please join our Discord server