Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Render Master CSS

mastercss_render_css
Read-onlyIdempotent

Generate CSS from an HTML fragment or a whitespace-separated class list to preview and verify the styles Master CSS will produce before applying changes.

Instructions

Generate CSS from an HTML fragment or a whitespace-separated class list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mastercss_render_css"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlNo
contextNo
classListNo

Output Schema

NameRequiredDescriptionDefault
resultYes
versionYes
metadataYes
diagnosticsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the safety profile is covered. The description adds nothing beyond that—no note on output shape, whether the two inputs can be combined, or what happens when neither is supplied (all parameters are optional).

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; the core purpose leads immediately. Its brevity shades into under-specification rather than padding, which is penalized in other dimensions rather than here.

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?

An output schema exists, so return values needn't be described, but the tool has three optional parameters, an unexplained enum, and 0% schema documentation. For a generator whose behavior depends heavily on which optional input is provided, the definition leaves too much for the agent to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It implicitly maps to `html` and `classList` but says nothing about mutual exclusivity, precedence when both are given, or the `context` enum values ("project" vs "preset"), leaving a third of the parameters entirely unexplained.

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 gives a specific verb ("Generate") and resource ("CSS") and distinguishes two input modes: an HTML fragment or a class list. It is clear what the tool produces, but it does not differentiate itself from siblings such as mastercss_extract_classes or mastercss_css_compare.

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 statement of when to choose this tool over mastercss_extract_classes, mastercss_scan_project, or mastercss_css_compare, and no prerequisites or exclusions. The two input modes are named but not framed as alternatives with conditions for picking one.

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