Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Suggest Master CSS Classes

mastercss_suggest_classes
Read-onlyIdempotent

Suggest project-aware Master CSS classes for an isolated CSS declaration block; preserve the full block when conversion needs review.

Instructions

Suggest project-aware classes for an isolated CSS declaration block. Preserves the complete block when conversion needs review. Checks declaration output, not surrounding cascade or browser rendering. Does not write files.

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": {
      "declarations": "<declarations>"
    },
    "name": "mastercss_suggest_classes"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNo
declarationsYes

Output Schema

NameRequiredDescriptionDefault
resultYes
versionYes
metadataYes
diagnosticsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behaviour, so the bar is lower, yet the description still adds real signal: it preserves the complete block when conversion needs review (a fallback path an agent must anticipate) and limits verification to declaration output rather than cascade or rendering. 'Does not write files' largely restates readOnlyHint, but the review-fallback and scope-of-checking notes are genuine additions.

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?

Four short sentences, front-loaded with the purpose and each subsequent clause adding a distinct constraint. Slightly telegraphic phrasing ('Checks declaration output') costs a little clarity but there is no filler.

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?

An output schema exists, so return values need not be described, and the safety profile is covered by annotations. What is missing is input-side detail: with zero schema description coverage, the two parameters — especially the project/preset enum — remain undefined, which is a meaningful gap for a tool whose whole job is context-sensitive output.

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 carries the full burden and does not meet it. 'Project-aware' hints at the context enum but never explains 'project' vs 'preset', and nothing says whether 'declarations' is raw CSS text, a property list, or a full block — despite the 32768-character cap implying substantial input.

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: 'Suggest project-aware classes for an isolated CSS declaration block', which tells an agent exactly what comes out and from what input. It scopes the input ('isolated declaration block') but never contrasts itself with plausible neighbours like mastercss_suggest_syntax or mastercss_extract_classes, so sibling differentiation is left to inference.

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 implied rather than stated: the 'isolated CSS declaration block' framing and 'Checks declaration output, not surrounding cascade or browser rendering' tell an agent the boundaries of applicability. There is no explicit when-to-use vs when-to-use-an-alternative guidance, and no indication of what to do when a whole stylesheet rather than a declaration block is at hand.

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