Generate a color scheme from a seed hex color by choosing a mode (monochrome, analogic, complement, triad, quad) and color count, so you can build consistent palettes for design.
Generate a color scheme from a seed hex color.
| Name | Required | Description | Default |
|---|---|---|---|
| hex | Yes | Seed hex color (e.g. FF5733). | |
| mode | No | Scheme mode: monochrome, analogic, complement, triad, quad (default: analogic). | |
| count | No | Number of colors (default 5, max 10). |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not disclose read-only nature, determinism, auth/rate limits, or return format; it only states that a scheme is generated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with the verb and resource front-loaded and no wasted words. It is appropriately sized for its minimal content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple generation tool, the schema covers all parameters, but with no annotations or output schema the description omits return format and mode behavior. It is minimally adequate but incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with detailed descriptions for hex, mode, and count. The description mentions the seed hex but adds no mode/count semantics beyond what the schema already provides, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Generate') and resource ('color scheme') plus the seed input, distinguishing it from random palette tools. It does not name or differentiate from siblings such as colormind_generate_palette or color_palette beyond the seed-hex source.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides no when-to-use guidance, prerequisites, or alternatives. The agent must infer that this is for seed-based scheme generation rather than other color/palette tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.