Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Trace Master CSS Class

mastercss_trace_class
Read-onlyIdempotent

Trace a Master CSS class from project extraction through generated CSS, missing CSS classification, and engine inspection to diagnose styling gaps.

Instructions

Trace one class from project extraction through generated CSS, missing CSS classification, and engine inspection.

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": {
      "className": "<className>"
    },
    "name": "mastercss_trace_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNo
patternsNo
classNameYes
includeCssNo

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, closed-world behavior, so the safety profile is covered. The description adds the useful detail that results span extraction through engine inspection rather than a single lookup, but says nothing about cost, whether a project scan must precede it, or how 'missing CSS classification' is determined.

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; the pipeline stages are listed in execution order. It is efficiently sized, though it spends its words on flow rather than on the parameters that need explaining.

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 annotations cover the safety profile. For a four-parameter tool with an enum and array argument, however, leaving all parameter meaning undocumented makes the definition only marginally complete.

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 largely fails: it hints that className is the subject ('one class') but never explains 'context' (project vs preset), 'patterns', or 'includeCss'. An agent must guess at the meaning and effect of three of four parameters.

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?

The description names a specific verb ('Trace') and resource ('one class') and enumerates the pipeline stages covered: project extraction, generated CSS, missing CSS classification, and engine inspection. That scope separates it from a narrow inspector like mastercss_inspect_class, though no sibling is named explicitly.

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 end-to-end pipeline framing implies the use case (debugging why one class did or didn't produce CSS), but it never states when to prefer this over the sibling inspect/extract tools, nor any preconditions such as having run a project scan first.

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