Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Inspect Master CSS Class

mastercss_inspect_class
Read-onlyIdempotent

Inspect a Master CSS class to get its semantic parts, generated rules, variables, and CSS text, helping trace how the class creates styles and debug issues.

Instructions

Inspect one Master CSS class and return semantic parts, generated rules, variables, and CSS text.

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

Input Schema

NameRequiredDescriptionDefault
contextNo
classNameYes

Output Schema

NameRequiredDescriptionDefault
resultYes
versionYes
metadataYes
diagnosticsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds that the result is decomposed into semantic parts, rules, variables, and CSS text — useful but essentially return-value content that the presence of an output schema already supplies. No disclosure of behavior for the 'context' switch or of any limits.

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, and the returned artifacts are enumerated efficiently. It is arguably too short for the semantic gaps it leaves, but nothing in it is wasted wording.

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 tool is simple (two parameters, read-only, has an output schema), so return-value detail need not be spelled out. Still, the meaning of the project/preset context choice is a material omission for an otherwise trivially callable tool.

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 must compensate and largely does not. It clarifies only that className refers to a single class, leaving the 'context' enum (project vs preset) completely unexplained in both schema and description — an agent cannot tell what switching context actually changes.

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 ('Inspect') and resource ('one Master CSS class') plus the artifacts returned (semantic parts, generated rules, variables, CSS text). The singular scope helps distinguish it from batch/extraction siblings, but it never names an alternative such as mastercss_trace_class or mastercss_inspect_directives, so the agent gains no explicit sibling differentiation.

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?

The description gives no when-to-use or when-not-to-use guidance. With siblings like mastercss_trace_class and mastercss_inspect_directives in the same space, an agent has to guess which inspection tool is appropriate from names alone.

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