Skip to main content
Glama
deepakkumardewani

Color Scheme Generator MCP Server

generate_triad_scheme

Generate triad color schemes with three evenly spaced colors on the color wheel for design projects. Input a seed color to create harmonious palettes.

Instructions

Generates a triad color scheme with three evenly spaced colors on the color wheel

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorYesThe seed color in hex (098765), RGB (0,71,171), or HSL (215,100%,34%) format
countNoNumber of colors to generate (3-10, default: 5)

Implementation Reference

  • Handler function for generate_triad_scheme tool: parses arguments, generates triad color scheme using shared helper, and returns JSON-formatted result.
    async (args) => {
      const { color, count } = args;
      const result = await generateColorScheme(color, "triad", count);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Registers the generate_triad_scheme tool with MCP server, including name, description, input schema, and handler.
    server.tool(
      "generate_triad_scheme",
      "Generates a triad color scheme with three evenly spaced colors on the color wheel",
      colorSchemeInputShape,
      async (args) => {
        const { color, count } = args;
        const result = await generateColorScheme(color, "triad", count);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      }
    );
  • Shared Zod schema for input validation of color scheme tools: requires seed color string and optional count (3-10).
    const colorSchemeInputShape = {
      color: z
        .string()
        .describe(
          "The seed color in hex (098765), RGB (0,71,171), or HSL (215,100%,34%) format"
        ),
      count: z
        .number()
        .int()
        .min(3)
        .max(10)
        .default(5)
        .optional()
        .describe("Number of colors to generate (3-10, default: 5)"),
    };
  • Core helper function that handles color parsing, API call to TheColorAPI for scheme generation in specified mode (e.g., 'triad'), and response formatting.
    async function generateColorScheme(
      color: string,
      mode: string,
      count: number = 5
    ) {
      const { param, value } = parseColorInput(color);
      const url = `https://www.thecolorapi.com/scheme?${param}=${value}&mode=${mode}&count=${count}&format=json`;
    
      try {
        const response = await fetch(url);
        if (!response.ok) {
          throw new Error(
            `Color API request failed: ${response.status} ${response.statusText}`
          );
        }
    
        const data: any = await response.json();
    
        if (!data.colors || !Array.isArray(data.colors)) {
          throw new Error("Invalid response from Color API");
        }
    
        // Format the response for better readability
        const colors = data.colors.map((color: any, index: number) => ({
          position: index + 1,
          hex: color.hex?.value || "N/A",
          rgb: color.rgb
            ? `rgb(${color.rgb.r}, ${color.rgb.g}, ${color.rgb.b})`
            : "N/A",
          hsl: color.hsl
            ? `hsl(${color.hsl.h}, ${color.hsl.s}%, ${color.hsl.l}%)`
            : "N/A",
          name: color.name?.value || "Unknown",
        }));
    
        return {
          scheme_mode: mode,
          seed_color: data.seed?.hex?.value || value,
          color_count: colors.length,
          colors: colors,
        };
      } catch (error) {
        console.error(`Error generating ${mode} color scheme:`, error);
        throw error;
      }
    }
  • Utility function to parse input color string into API-compatible parameter (hex, rgb, hsl) and value.
    function parseColorInput(color: string): { param: string; value: string } {
      const cleanColor = color.trim();
    
      // Check for hex format
      if (cleanColor.startsWith("#")) {
        return { param: "hex", value: cleanColor.substring(1) };
      } else if (/^[0-9A-Fa-f]{6}$/.test(cleanColor)) {
        return { param: "hex", value: cleanColor };
      }
    
      // Check for RGB format
      if (
        cleanColor.toLowerCase().includes("rgb") ||
        /^\d+,\d+,\d+$/.test(cleanColor)
      ) {
        const rgbMatch = cleanColor.match(/(\d+),\s*(\d+),\s*(\d+)/);
        if (rgbMatch) {
          return {
            param: "rgb",
            value: `${rgbMatch[1]},${rgbMatch[2]},${rgbMatch[3]}`,
          };
        }
      }
    
      // Check for HSL format
      if (cleanColor.toLowerCase().includes("hsl") || cleanColor.includes("%")) {
        const hslMatch = cleanColor.match(/(\d+),\s*(\d+)%,\s*(\d+)%/);
        if (hslMatch) {
          return {
            param: "hsl",
            value: `${hslMatch[1]},${hslMatch[2]}%,${hslMatch[3]}%`,
          };
        }
      }
    
      // Default to hex if format is unclear
      return { param: "hex", value: cleanColor.replace("#", "") };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool generates colors but doesn't cover aspects like whether it's deterministic, if there are rate limits, error handling for invalid inputs, or the format of the output (e.g., list of hex codes). This leaves significant gaps for an agent to understand how to invoke it effectively.

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?

The description is a single, efficient sentence that front-loads the core purpose without unnecessary details. Every word earns its place by specifying the tool's function and key characteristic (three evenly spaced colors), making it easy to scan and understand quickly.

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

Completeness2/5

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

Given the complexity of a color generation tool with no annotations and no output schema, the description is insufficient. It doesn't explain the return values (e.g., format of generated colors), error conditions, or behavioral traits like idempotency. For a tool that likely produces structured color data, more context is needed to ensure reliable agent usage.

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 the input schema already fully documents the parameters 'color' and 'count'. The description adds no additional meaning beyond what the schema provides, such as explaining how 'color' influences the triad generation or clarifying the relationship between 'count' and the triad concept. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the action ('Generates') and resource ('a triad color scheme'), specifying it produces 'three evenly spaced colors on the color wheel'. However, it doesn't explicitly differentiate from sibling tools like 'generate_quad_scheme' or 'generate_complement_scheme', which would require mentioning the specific triad pattern versus other color schemes.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description lacks context about scenarios where a triad scheme is preferred over monochrome, complementary, or other sibling schemes, and there are no exclusions or prerequisites mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/deepakkumardewani/color-scheme-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server