Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Scan Master CSS Project

mastercss_scan_project
Read-onlyIdempotent

Scans source files and stylesheet entries to capture a resolved project state for impact comparison, and inspects design-system token references and policies.

Instructions

Scan source files and stylesheet entries. Set includeSnapshot to capture a resolved project state for later impact comparison. Pass designSystem to inspect stylesheet token references and design policies; add routeStylesheets globs for stylesheets imported from JavaScript.

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

Input Schema

NameRequiredDescriptionDefault
classesNo
contextNo
patternsNo
includeCssNo
designSystemNo
includeSnapshotNo
routeStylesheetsNo

Output Schema

NameRequiredDescriptionDefault
resultYes
versionYes
metadataYes
diagnosticsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.2/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, so the safety profile is covered. The description adds real value by explaining that includeSnapshot materializes a resolved project state that can be compared later - a side effect of sorts - which is not visible in the annotations. It says nothing about what files are scanned by default, cost/time on large projects, or how the snapshot is retained between calls.

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?

Three short sentences, front-loaded with what the tool does, then parameter-oriented guidance; nearly every clause carries information. Minor density issues ("add routeStylesheets globs") but 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 and full annotations relieve the description of explaining return values and safety, and it correctly uses its space on the parameters that have cross-tool consequences. However, for a 7-parameter tool with a nested object and zero schema descriptions, leaving the core scoping parameters (classes, patterns, context, includeCss) undefined makes the definition only marginally sufficient.

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 7 parameters, so the description carries the full explanatory burden, yet it only addresses 3 of them (includeSnapshot, designSystem, routeStylesheets). The concepts of classes, context (project vs preset), patterns, and includeCss - arguably the core filtering semantics of a scan - are never explained, nor are the nested designSystem fields (rawValuePolicy, metadata, deprecated/replacement).

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?

"Scan source files and stylesheet entries" gives a specific verb and two clear resources, so an agent knows it walks a project and collects CSS-relevant entries. It stops short of differentiating the scan-and-collect purpose from a sibling like mastercss_lint_project, which an agent could plausibly confuse it with.

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?

The description does give conditional guidance tied to parameters: includeSnapshot when you need state "for later impact comparison" (implicitly before mastercss_css_compare), designSystem when checking token references and policies, routeStylesheets for JS-imported stylesheets. What's missing is any statement of when to choose this tool over mastercss_lint_project or a workspace/inspect sibling, and whether it should be run before or after those.

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