Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Lint Master CSS Content

mastercss_lint_content
Read-onlyIdempotent

Run Master CSS class-list diagnostics on an in-memory source buffer without writing files, so you can preview and validate classes before changes.

Instructions

Run Master CSS class-list diagnostics on an in-memory source buffer without writing 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": {
      "content": "<content>",
      "filePath": "<filePath>"
    },
    "name": "mastercss_lint_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesNo
contentYes
contextNo
filePathYes

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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description usefully confirms no file writes occur. It does not disclose what the diagnostics return, how severities are reported, or why filePath is mandatory for an in-memory buffer.

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 zero filler; the mutation-safety qualifier is placed well. It is perhaps too terse for a four-parameter tool, but nothing is wasted.

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 need not be described, but with 0% parameter coverage and two required parameters the definition leaves too much for the agent to guess. The required filePath semantics in particular are a real completeness hole.

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 four parameters, so the description carries the full burden and adds almost nothing. The required filePath for in-memory content is genuinely confusing and unexplained, as are the 'rules' string and the 'project'/'preset' context enum.

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: run Master CSS class-list diagnostics against an in-memory source buffer. The 'in-memory source buffer' phrasing also implicitly distinguishes it from mastercss_lint_project, though the sibling is never named.

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?

'Without writing files' implies this is the choice when content is not yet on disk, versus project-level linting. That is only an implication — there is no explicit when-to-use statement and no named alternative.

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