Skip to main content
Glama

Audit Tailwind config

audit_tailwind

Analyze Tailwind configuration files to identify legacy HeroUI patterns for migration to HeroUI v3.

Instructions

Analyze a Tailwind configuration file for legacy HeroUI patterns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes

Implementation Reference

  • Registration and handler for the `audit_tailwind` tool in `src/server.ts`. It imports `analyzeTailwindConfig` from `src/core/migration.js` and returns the analysis results.
    server.registerTool(
      "audit_tailwind",
      {
        title: "Audit Tailwind config",
        description: "Analyze a Tailwind configuration file for legacy HeroUI patterns.",
        inputSchema: { code: z.string() }
      },
      async ({ code }) => {
        const { analyzeTailwindConfig } = await import("./core/migration.js");
        const result = analyzeTailwindConfig(code);
        return { content: [], structuredContent: result as any };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. While 'analyze' implies a read-only operation, the description does not disclose auth requirements, side effects, rate limits, or what the analysis output format/structure looks like.

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?

Single sentence that is front-loaded and efficiently structured. Every word earns its place—no redundancy or boilerplate.

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?

Adequate for a single-parameter tool but incomplete given the lack of annotations and output schema. The description covers the core purpose but omits expected return values, error conditions, or behavioral constraints that would help an agent invoke the tool effectively.

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 0%, requiring the description to compensate. It partially compensates by implying the 'code' parameter should contain Tailwind configuration content, but does not explicitly document the parameter semantics, format requirements, or validation rules.

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?

Specific verb (analyze), resource (Tailwind configuration file), and scope (legacy HeroUI patterns) are clearly stated. However, it does not explicitly differentiate from the sibling 'analyze_file' tool, which is more generic.

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 explicit guidance on when to use this tool versus 'analyze_file' or other siblings. No mention of prerequisites or when not to use it. Usage is only implied by the specific domain 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/sctg-development/heroui-migration-mcp'

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