Skip to main content
Glama

get_color_palette

Retrieve the complete color palette from Korea's government digital design system (KRDS) for use in official digital services and UI development.

Instructions

KRDS 전체 색상 팔레트를 가져옵니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function implementing the get_color_palette tool logic by searching for 'color' tokens using the KRDSLoader.
    export async function getColorPalette(loader: KRDSLoader): Promise<TokenSearchResult[]> {
      return await loader.searchTokens('color');
    }
  • MCP server handler for the get_color_palette tool, which calls the core getColorPalette function and formats the output as a formatted text response.
    private async handleGetColorPalette() {
      const colors = await getColorPalette(this.loader);
      
      const text = `KRDS 색상 팔레트 (${colors.length}개):\n\n` +
        colors.slice(0, 30).map(color => 
          `🎨 ${color.name}: ${color.value}`
        ).join('\n') +
        (colors.length > 30 ? `\n\n... 그 외 ${colors.length - 30}개 색상` : '');
      
      return {
        content: [{ type: 'text', text }],
      };
    }
  • src/index.ts:168-175 (registration)
    Registration of the get_color_palette tool in the tools list, including name, description, and input schema (empty object).
    {
      name: 'get_color_palette',
      description: 'KRDS 전체 색상 팔레트를 가져옵니다.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:72-73 (registration)
    Switch case in tool call handler that routes 'get_color_palette' requests to the specific handler method.
    case 'get_color_palette':
      return await this.handleGetColorPalette();
  • Input schema definition for the get_color_palette tool (accepts no parameters).
    inputSchema: {
      type: 'object',
      properties: {},
    },
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 only states what the tool does (fetches the color palette) without mentioning critical details like whether it's a read-only operation, if it requires authentication, rate limits, or what the return format looks like. This leaves significant gaps in understanding how the tool behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple tool with no parameters. However, it could be slightly more informative by adding context, but it's not wasteful.

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 tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal but insufficient. It lacks details on what 'KRDS' refers to, the format of the returned color palette, or any behavioral traits. For a tool that might return complex data (like a color palette), more context is needed to be complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description appropriately doesn't add parameter details, as none are needed. A baseline score of 4 is applied since no parameters exist, and the description doesn't attempt to compensate for non-existent gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'gets the entire KRDS color palette' (가져옵니다 = gets/fetches), which provides a basic verb+resource combination. However, it doesn't differentiate from sibling tools like 'search_design_tokens' or 'get_krds_resources' that might also retrieve color-related data, leaving the scope ambiguous. The purpose is clear but lacks specificity about what makes this tool unique.

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 doesn't mention prerequisites, context, or exclusions, and it fails to reference sibling tools that might offer overlapping or complementary functionality. Users must infer usage based on the tool name alone.

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/re-rank/UIUX-MCP'

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