Skip to main content
Glama

css_to_tailwind

Read-onlyIdempotent

Converts raw CSS declarations into deterministic Tailwind utility classes, so you can migrate styles to Tailwind without guessing at equivalents.

Instructions

Convert raw CSS declarations into deterministic Tailwind utility classes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "css": "<css>"
    },
    "name": "css_to_tailwind"
  }
}

Input Schema

NameRequiredDescriptionDefault
cssYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description's only added behavioral claim is 'deterministic', which largely restates idempotency; it says nothing about unsupported CSS constructs, conflicting declarations, error behavior, or whether the output is one class string or several.

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?

One front-loaded sentence with no filler or redundancy. It is efficient, though the brevity comes at the cost of the missing usage and input-format detail noted elsewhere.

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?

With no output schema and an undocumented parameter, the description is the only source of truth for input format and return shape, and it supplies neither. For a compile/transform tool, an agent needs to know what the input string must contain and what comes back, and this definition leaves both open.

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 single 'css' parameter has 0% schema description coverage, so the description must carry the meaning. 'Raw CSS declarations' does signal that the input is a CSS declaration string rather than a file path or full stylesheet, which is useful, but it does not clarify scope (declarations only vs. selectors/rules) or accepted syntax.

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 states a specific verb ('Convert') and both the source and target resource ('raw CSS declarations' into 'Tailwind utility classes'), which is unambiguous. It does not explicitly differentiate itself from related siblings like generate_color_palette or generate_responsive_breakpoints, but the transformation is distinct enough to be recognizable on its own.

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?

There is no guidance on when to choose this tool over the nearby generation tools, and no stated preconditions or exclusions. The agent must infer that this is the tool for CSS-to-Tailwind translation purely from the name and purpose sentence.

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