Skip to main content
Glama
krusch-frontend-mcp

krusch-frontend-mcp

by kruschdev

generate_color_palette

Read-onlyIdempotent

Generate a cohesive color palette (complementary, analogous, triadic) and contrast scores from a base hex code to quickly build accessible, harmonious color schemes.

Instructions

Generates a cohesive color palette (complementary, analogous, triadic) and contrast scores from a base hex code.

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": {
      "baseHex": "<baseHex>"
    },
    "name": "generate_color_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseHexYesThe base color in #RRGGBB format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description's added value is disclosing the return contents — a palette plus contrast scores — which no output schema provides, and the fixed palette schemes tell the agent what variety to expect. It stops short of stating output shape or whether all schemes return at once.

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 sentence, front-loaded with the verb and result, listing the palette types and the contrast-score output. Every clause carries information and there is no filler.

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 one-parameter, read-only generator with rich annotations, the definition covers input, output content, and palette variants — enough to call it correctly. Not fully complete: it does not say whether the output contains all three schemes or one selected scheme, which matters because that selection is not exposed as a parameter.

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 a single required parameter with 100% schema description coverage, and the schema already specifies the #RRGGBB format. The description only reiterates 'from a base hex code', adding no new semantics such as case sensitivity or shorthand handling; baseline 3 applies when the schema does the documentation work.

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?

States a specific verb (generates), a specific resource (cohesive color palette), the concrete variants (complementary, analogous, triadic), and the derived output (contrast scores) from a base hex code. Nothing in the sibling list (CSS variables, templates, breakpoints) overlaps, so an agent can route this without opening the schema.

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?

Usage is implied by the purpose: call it when you need a palette derived from a single hex color. There is no explicit when/when-not framing, no statement of prerequisites beyond the hex format, and no named alternative — acceptable for a narrow pure-function tool, but it leaves the agent to infer the trigger condition.

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