Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Inspect Master CSS Directives

mastercss_inspect_directives
Read-onlyIdempotent

Inspect CSS-first directives from a stylesheet entry or in-memory CSS and report their manifest and generated CSS effects for debugging and validation.

Instructions

Inspect CSS-first directives from a stylesheet entry or in-memory CSS content and report manifest/CSS effects.

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

Input Schema

NameRequiredDescriptionDefault
contentNo
contextNo
filePathNo
entryPathNo
preserveNativeCSSNo

Output Schema

NameRequiredDescriptionDefault
resultYes
versionYes
metadataYes
diagnosticsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

C2.7/5.0
Behavior2/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 only 'report manifest/CSS effects', which is vague and leaves key behavior unexplained, such as how entryPath, filePath, and content interact or which one wins when several are supplied.

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 efficiently sized, though the brevity comes at the cost of the parameter detail noted elsewhere.

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 explained, but for a tool with five optional, mutually related inputs at 0% schema coverage the description is well short of what an agent needs to construct a correct call.

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 five parameters, so the description must compensate and it largely does not. It hints that 'content' is in-memory CSS and that a 'stylesheet entry' relates to entryPath, but context (project vs preset), filePath, and preserveNativeCSS are given no meaning at all.

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 (CSS-first directives) and identifies the two input sources (stylesheet entry or in-memory CSS), which is clear enough to act on. It does not distinguish itself from the sibling mastercss_preview_directive_format, so an agent could still struggle to pick between them.

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 guidance, no mention of prerequisites, and no reference to any alternative tool. The agent must infer from the name alone that this is a read-only inspection step versus the preview or lint siblings.

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