Skip to main content
Glama

palette

Fetch live color schemes from Color Hunt, convert color JSON into CSS, Tailwind, SCSS, Figma, Android, or Swift, or generate light/dark/high-contrast/muted/vivid variants.

Instructions

Fetch live palettes from Color Hunt, convert palette JSON into CSS/Tailwind/SCSS/Figma/Android/Swift, or generate light/dark/high-contrast/muted/vivid variants. Select action: fetch, convert, or variants.

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": {
      "action": "<action>"
    },
    "name": "palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoFetch mode (required for fetch)
limitNoNumber of palettes (default 5)
queryNoSearch query (when mode=query)
themeNoTheme name (when mode=theme)
actionYesPalette operation
colorsNoHex colors required for variants, e.g. ["#3b82f6"]
formatNoFetch output format (default json)
targetNoConversion target (required for convert)
palettesNoPalette array required for convert

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the external dependency ('live palettes from Color Hunt'), which is genuinely useful, but says nothing about rate limits, failure/offline behavior, whether results are cached, or what any action returns. For a three-mode tool with no output schema, that is a substantial gap.

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?

Two dense sentences that front-load the three capabilities before the action selector. Nothing is redundant, and the parallel enumeration of formats and variants is easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter, three-operation tool with no annotations and no output schema, the description covers what the tool can do but omits defaults, return shapes, and error behavior. The unexplained mapping between the five named variant families and the actual parameters is the most significant hole.

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 the schema already documents all nine parameters; baseline 3 applies. The description adds some meaning by enumerating the six conversion targets and five variant families, but it introduces variant types (light/dark/high-contrast/muted/vivid) for which no corresponding parameter exists, leaving the variant-selection mechanism unclear.

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?

The description names three concrete operations with specific verbs and resources: fetching live palettes from Color Hunt, converting palette JSON to six named targets, and generating five named variant families. That makes the tool's scope unmistakable. It doesn't distinguish itself from any sibling tool, so it stops short of a 5.

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?

'Select action: fetch, convert, or variants' is the only routing guidance, and it essentially restates the action enum rather than telling the agent when each mode is appropriate. There is no mention of when not to use the tool or of prerequisites such as network availability. Usage is implied but not explained.

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