Skip to main content
Glama

generate_palette_with_locks

Read-onlyIdempotent

Generate a color palette while preserving specified locked colors, using perceptual color spaces to keep chosen colors intact and produce cohesive, contrasting, or gradient results.

Instructions

Generate a color palette while preserving specific locked colors. Uses deterministic perceptual search in OKLCH/HCT/LAB/HSL and avoids universally disliked colors.

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": {
      "lockedColors": "<lockedColors>",
      "totalColors": "<totalColors>"
    },
    "name": "generate_palette_with_locks"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoGeneration mode: harmony (cohesive), contrast (distinct), or gradient (smooth transition)harmony
colorSpaceNoColor space for palette generation/interpolation (oklch/hct/lab are perceptually uniform)oklch
totalColorsYesTotal number of colors in the final palette
lockedColorsYesColors that must be included in the palette

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds genuinely new behavioral facts: the search is deterministic and perceptual across specific spaces, and it filters out universally disliked colors, which tells the agent the output quality is constrained rather than random. It does not say what happens on locked-color/size conflicts or what the return shape looks like.

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 sentences, no filler, and the distinguishing constraint is front-loaded ahead of the algorithmic detail. Every clause carries information an agent can act on.

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?

For a four-parameter, fully documented, annotated, read-only tool this covers what the agent needs to select and call it. The remaining gap is small: no output schema exists, so a brief note on the return value and on handling impossible locked-color sets would round it out.

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%, so all four parameters (mode, colorSpace, totalColors, lockedColors) are already documented with enums and ranges. The description only echoes the locked-colors parameter and adds no syntax detail, format expectations, or interaction rules beyond the schema.

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 and resource ('Generate a color palette') plus a distinguishing constraint ('preserving specific locked colors') that separates it from the plain generate_palette sibling. It stops short of explicitly naming an alternative tool to use when no colors are locked.

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 condition for choosing this tool is only implied: use it when some colors must survive generation. There is no explicit when-not guidance, no mention of how it differs from generate_palette or harmonize_colors, and no prerequisites such as needing valid color strings.

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