Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Preview Master CSS Fixes

mastercss_preview_fixes

Preview lint fixes or generated CSS as a diff and get a confirmation token before applying changes. Use it to review Master CSS updates before writing them.

Instructions

Create a diff preview for lint fixes or generated CSS output and return a confirmation token.

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_preview_fixes"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
rulesNo
ttlMsNo
contextNo
patternsNo
outputPathNo

Output Schema

NameRequiredDescriptionDefault
resultYes
versionYes
metadataYes
diagnosticsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety posture is partly covered. The description does add real context by framing the call as a preview that yields a confirmation token rather than applying changes, but it omits how long the token lives, whether the token must be redeemed elsewhere, and whether outputPath actually writes to disk.

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, so every word earns its place. The brevity costs it somewhat since the sentence is compressed at the expense of workflow detail an agent needs.

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 6 parameters at 0% description coverage, an output schema present (so return values are covered) and a two-phase preview/confirm design, the description is too thin. It should at minimum explain the token lifecycle, what outputPath does, and when each mode applies.

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% across 6 parameters, so the description needed to compensate and does not. It only loosely gestures at the 'mode' enum values ('lint fixes or generated CSS output') and says nothing about rules, ttlMs, context, patterns, or whether outputPath causes a file to be written.

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 and resource: create a diff preview for either lint fixes or generated CSS, plus a confirmation token. It is clear what the tool produces, though it never names how it differs from the adjacent preview/apply/compare siblings (mastercss_apply_preview, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied through the phrase 'return a confirmation token', which hints at a preview-then-apply workflow, but the definition never says when to pick this over mastercss_apply_preview or mastercss_css_compare, nor which mode to choose for a given situation. No exclusions or prerequisites are given.

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