Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Color palette generator: harmonies and shades from one color

color_palette
Read-only

Build a colour palette from one hex colour: complementary, analogous, triadic, split-complementary and tetradic harmonies (hue rotations at the same saturation and lightness), plus six shades from light to dark, all as hex codes, with the base colour's HSL. Use for UI themes, charts, brand kits or slide decks; to check text readability on a colour use color_contrast. Example: color=#3366ff. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "color": "<color>"
    },
    "name": "color_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYesBase colour as hex, such as #3366ff or 36f

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, non-destructive and non-open-world behavior, but the description adds meaningful context: harmony generation is defined as hue rotations at the same saturation and lightness, six shades are returned, billing is per call, failed calls are free, and repeats are not free. This adds cost and computation behavior beyond the structured annotations without contradicting them.

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?

The purpose and output contents are front-loaded, followed by use cases, an example, and pricing. It is slightly verbose around billing and idempotence, but the information is relevant and organized.

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?

Given the simple one-parameter input, absence of an output schema, and existing annotations, the description supplies what the agent needs: what is generated, the return format in broad terms, when to use it, cost model, and safety behavior.

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?

There is only one parameter and schema description coverage is 100%, so the schema already explains the hex colour input. The description adds an example value but no additional syntax or validation detail beyond the schema.

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 gives a specific verb and resource: build a palette from one hex colour, naming exactly which harmonies and shades are produced. It also distinguishes the tool from color_contrast by routing readability checks elsewhere.

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?

It explicitly lists relevant use cases (UI themes, charts, brand kits, slide decks) and names the alternative tool for text readability. The caller knows both when to use this tool and which sibling to choose instead for contrast checks.

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.