Skip to main content
Glama

export_palette

Read-onlyIdempotent

Export a color palette as CSS custom properties, SCSS variables, Tailwind config, W3C design tokens, JSON, or a DESIGN.md colors block, with optional names and prefixes for each token.

Instructions

Export a list of colors as CSS custom properties, SCSS variables, a Tailwind config snippet, W3C design tokens, JSON, or a DESIGN.md colors: block.

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": {
      "colors": "<colors>",
      "format": "<format>"
    },
    "name": "export_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesNoOptional names for each color. Length must match colors. Defaults to a 50/100…900 scale.
colorsYesPalette colors (up to 256)
formatYesOutput format: css (custom properties), scss (variables), tailwind (config), tokens (W3C design tokens), json, design-md (DESIGN.md `colors:` YAML for the front matter)
prefixNoOptional prefix for variable/token names (e.g. 'brand')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and closed-world behavior, so the safety profile is covered. The description adds that output is emitted as one of six named code/config syntaxes, which is real context beyond annotations, but it never says whether the result is returned as a string or written to disk, nor whether the palette is validated or reordered during export.

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?

One front-loaded sentence with the action first and the six output targets listed after. No filler, no restatement of the title or name.

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?

With no output schema, the description sensibly enumerates what each format yields (CSS custom properties, SCSS variables, Tailwind config, W3C tokens, JSON, DESIGN.md front matter), which is the key unknown for an exporter. Minor gap: it does not state the return container or whether invalid/duplicate colors are handled.

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%, including a full enum for format, so the schema already carries the parameter burden. The description's format enumeration largely restates the enum values and adds nothing about prefix or names semantics, so baseline 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?

States a specific verb (Export) and resource (a list of colors) and enumerates the concrete output artifacts, so the agent knows this is a serialization tool rather than a generator. It does not name or rule out the closest sibling (generate_theme_css), so the boundary between 'export my colors' and 'generate theme CSS' is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The format list implies when the tool is useful (converting an existing palette into a target file syntax), but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must reason about the export-vs-generate split on its own.

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