Skip to main content
Glama
krusch-frontend-mcp

krusch-frontend-mcp

by kruschdev

css_to_tailwind

Read-onlyIdempotent

Converts raw CSS rules into Tailwind utility classes, helping developers migrate styles and standardize frontend code.

Instructions

Translates standard CSS properties into 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": {
      "cssString": "<cssString>"
    },
    "name": "css_to_tailwind"
  }
}

Input Schema

NameRequiredDescriptionDefault
cssStringYesRaw CSS rules (e.g. 'display: flex; padding: 1rem;')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered externally. The description adds no behavioral context of its own: no note on coverage of unsupported CSS properties, no fidelity caveats (e.g. values with no Tailwind equivalent), and no indication of what the returned string 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.

Conciseness4/5

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

A single front-loaded sentence with no filler, and the direction of the transformation is unambiguous. It is efficient, though its brevity is partly the same brevity that leaves the behavior and output shape unstated.

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?

This is a low-complexity, single-parameter, non-destructive pure function, so a one-liner is defensible. However, with no output schema present, the description is the only place a caller could learn the shape of the result (one class string? one line per property?) and it says nothing about that, nor about unsupported-property handling.

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 100% and the single cssString parameter already has an inline example ('display: flex; padding: 1rem;'). The description adds no meaning beyond the schema, so the baseline of 3 applies for a well-documented single parameter.

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?

States a specific verb ('Translates') and a specific resource pair ('standard CSS properties into Tailwind utility classes'), which is enough for an agent to know exactly what transformation happens. It stops short of differentiating itself from siblings like generate_component_styles or get_canonical_template, so it is clear but not sibling-aware.

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 reach for this versus the sibling styling tools, nor any exclusions. Nothing tells the agent whether the input must be a complete rule set, whether unsupported properties are dropped or passed through, or whether arbitrary-value output is possible.

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