Skip to main content
Glama

Get the Cultural Story of a Colour

colour_story
Read-only

Provides cultural history for any hex color, detailing its meanings, archive names, and historical appearances. Designed for image prompts, brand storytelling, and creative briefs.

Instructions

Given a hex value, returns a rich narrative about that colour's cultural journey — where it has appeared in history, what it has meant to different civilisations, and what archive names it carries. Essential for image generation prompts, brand storytelling, and creative briefs. Example: '#DC143C' returns the story of crimson from Byzantine imperial courts through Tudor England to modern sport.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hexYesHex value e.g. '#DC143C'
n_archivesNoNumber of archive sources to draw from (default 5)

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, and the description is consistent with a read-only operation. The description adds context about the narrative covering cultural journey, history, civilizations, and archive names, which goes beyond the annotation.

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: two sentences plus an example, front-loaded with the core purpose, and every sentence adds value. No fluff.

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?

The description explains the return value (rich narrative about cultural journey, history, civilizations, archive names) and usage contexts. Given that an output schema exists, the description is adequately complete.

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?

Both parameters (hex, n_archives) are fully described in the schema with descriptions. The description provides an example hex value and explains what the tool does, but does not add significant meaning beyond the schema for the parameters themselves.

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 returns a rich narrative about a color's cultural journey given a hex value. It specifies the verb (returns), resource (cultural story of a colour), and distinguishes from siblings like colour_dna, colour_forensics, etc., which focus on different aspects.

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?

The description mentions the tool is essential for image generation prompts, brand storytelling, and creative briefs, indicating when to use it. However, it does not explicitly state when not to use it or contrast with similar siblings, leaving some ambiguity.

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