Skip to main content
Glama
CarbonoDev

TailwindCSS MCP Server

by CarbonoDev

get_tailwind_colors

Retrieve TailwindCSS color palette details including shades and hex values for design consistency and development workflows.

Instructions

Get TailwindCSS color palette information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorNameNoSpecific color name (e.g., 'blue', 'red')
includeShadesNoInclude all color shades (default: true)

Implementation Reference

  • The handler for the get_tailwind_colors tool, which delegates to the utilityMapper service.
    private async handleGetTailwindColors(args: any): Promise<any> {
      try {
        const params = this.validateGetColorsParams(args);
        const colors = await this.utilityMapper.getColors(params);
        return this.createSuccessResponse(colors);
      } catch (error) {
        this.handleServiceError(error, "Failed to get TailwindCSS colors");
      }
    }
  • The actual implementation logic that retrieves color information and filters shades if required.
    async getColors(params: GetColorsParams): Promise<ColorInfo[]> {
      let colors = this.getColorInfo(params.colorName);
      
      if (!params.includeShades) {
        // Filter out shade details if requested
        colors = colors.map(color => ({
          ...color,
          shades: {},
        }));
      }
    
      return colors;
    }
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 what the tool does ('Get... information') but doesn't describe how it behaves: whether it returns structured data or raw text, if it has rate limits, authentication requirements, error conditions, or what format the color information comes in. For a tool with zero annotation coverage, this is a significant gap in behavioral context.

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 extremely concise at just one sentence ('Get TailwindCSS color palette information'), with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple lookup tool. Every word earns its place by clearly communicating the tool's function.

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

Completeness3/5

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

Given the tool's apparent simplicity (2 optional parameters, no output schema, no annotations), the description is minimally complete but lacks important context. It doesn't explain what format the color information returns (e.g., JSON, CSS values, hex codes), whether it covers all Tailwind colors or a subset, or how it relates to sibling tools. For a tool with no output schema, the description should ideally provide some indication of return values.

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?

The input schema has 100% description coverage, with clear descriptions for both parameters ('colorName' and 'includeShades'). The tool description adds no parameter-specific information beyond what the schema already provides. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting for parameter documentation.

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 tool's purpose as 'Get TailwindCSS color palette information', which is a specific verb ('Get') + resource ('TailwindCSS color palette information'). It distinguishes from most siblings like 'convert_css_to_tailwind' or 'install_tailwind', but doesn't explicitly differentiate from 'generate_color_palette' or 'search_tailwind_docs' which might also involve color information.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when this tool is appropriate, when to use sibling tools like 'generate_color_palette' (which might create new palettes) or 'search_tailwind_docs' (which might provide broader documentation), or any prerequisites or context for usage.

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/CarbonoDev/tailwindcss-mcp-server'

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