Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Lint Master CSS Project

mastercss_lint_project
Read-onlyIdempotent

Run Master CSS class-list diagnostics and return fix proposals without writing files.

Instructions

Run Master CSS class-list diagnostics and return fix proposals without writing files.

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

Input Schema

NameRequiredDescriptionDefault
rulesNo
contextNo
patternsNo

Output Schema

NameRequiredDescriptionDefault
resultYes
versionYes
metadataYes
diagnosticsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

C2.9/5.0
Behavior3/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 description's "without writing files" is corroborating rather than new. The phrase "return fix proposals" usefully discloses that the output is a proposal set, not applied changes, which is genuine value beyond the annotations.

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 or repetition. It is efficient, though the compression comes partly at the cost of the missing parameter and usage detail noted above.

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?

The annotations cover the safety profile and an output schema exists, so return-value explanation is not needed. The remaining gap is the three undocumented optional parameters, whose effect on diagnostic scope an agent cannot determine from either the description or the schema.

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

Parameters1/5

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

Schema description coverage is 0% across three parameters, and the description supplies no meaning for any of them. The words "class-list" do not explain what 'rules' does, what the 'project' vs 'preset' context enum selects, or what form 'patterns' takes, and there is no default behavior stated for omitting them.

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?

"Run Master CSS class-list diagnostics and return fix proposals" states a specific verb and resource, and the "without writing files" clause distinguishes it from an apply/fix tool. It does not, however, say how it differs from the similarly named siblings such as mastercss_lint_content or mastercss_scan_project, so an agent still has to guess which lint entry point to use.

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 when-to-use or when-not-to-use guidance and no mention of alternatives. Given the presence of mastercss_apply_preview and mastercss_preview_fixes, the description should state that this is the analyze-only path and that fixes must be applied elsewhere, but it does not.

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