Skip to main content
Glama
CarbonoDev

TailwindCSS MCP Server

by CarbonoDev

get_tailwind_utilities

Retrieve TailwindCSS utility classes by category, CSS property, or search term to find styling solutions for web development projects.

Instructions

Get TailwindCSS utilities by category, property, or search term

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by utility category (e.g., 'layout', 'typography', 'colors')
propertyNoFilter by CSS property (e.g., 'margin', 'color', 'font-size')
searchNoSearch term to find utilities

Implementation Reference

  • The tool handler that receives the request, validates parameters, and calls the utility service to fetch utilities.
    private async handleGetTailwindUtilities(args: any): Promise<any> {
      try {
        const params = this.validateGetUtilitiesParams(args);
        const utilities = await this.utilityMapper.getUtilities(params);
        return this.createSuccessResponse(utilities);
      } catch (error) {
        this.handleServiceError(error, "Failed to get TailwindCSS utilities");
      }
    }
  • The core implementation of the utility fetching logic within UtilityMapperService.
    async getUtilities(params: GetUtilitiesParams): Promise<TailwindUtility[]> {
      let utilities: TailwindUtility[] = [];
    
      if (params.category) {
        utilities = this.getUtilitiesByCategory(params.category);
      } else if (params.property) {
        utilities = this.getUtilitiesByProperty(params.property);
      } else if (params.search) {
        utilities = this.searchUtilities(params.search);
      } else {
        // Return all utilities if no filter specified
        utilities = Array.from(this.utilityMap.values());
      }
    
      return utilities;
    }
  • src/index.ts:96-96 (registration)
    Registration of the tool in the listTools response.
    name: "get_tailwind_utilities",
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 describes a read operation ('Get') but doesn't mention any behavioral traits such as response format, pagination, rate limits, or error handling. This leaves significant gaps for an agent to understand how to interact with the tool 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 any wasted words. It directly communicates the tool's function and filtering options, making it easy to parse and understand quickly.

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 moderate complexity (3 optional parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and parameters but lacks details on behavioral traits and output, which are necessary for full contextual understanding, especially without annotations to fill in gaps.

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 schema description coverage is 100%, with clear descriptions for each parameter in the input schema. The description adds minimal value by listing the filtering criteria ('category, property, or search term') but doesn't provide additional syntax, format details, or examples beyond what the schema already covers, meeting the baseline for high schema coverage.

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 ('Get') and resource ('TailwindCSS utilities') with specific filtering criteria ('by category, property, or search term'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'get_tailwind_colors' or 'search_tailwind_docs', which is why it doesn't reach a 5.

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 like 'get_tailwind_colors' for color-specific utilities or 'search_tailwind_docs' for broader documentation searches. It implies usage through the filtering options but offers no explicit context or exclusions.

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