Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Apply Master CSS Preview

mastercss_apply_preview
Destructive

Applies a previously generated preview token after validating hashes and workspace containment, ensuring CSS changes are safe before writing them.

Instructions

Apply a previously generated preview token after validating hashes and workspace containment.

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": {
      "confirmToken": "<confirmToken>"
    },
    "name": "mastercss_apply_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmTokenYes

Output Schema

NameRequiredDescriptionDefault
resultYes
versionYes
metadataYes
diagnosticsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuinely new behavioral context — that hashes and workspace containment are validated before applying — but does not say what is actually mutated, whether the change is reversible, or what a rejected token returns.

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 mutating verb leads. Its brevity borders on under-specification for a destructive operation, but no sentence is wasted.

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. However, for a destructive, non-idempotent apply step, the definition should say what artifact is written and what a failed hash/containment validation produces; those gaps keep it at minimum-viable completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% with one parameter, so the description carries real weight; 'previously generated preview token' explains the origin and provenance constraint of confirmToken, which the bare string schema does not. It still omits format, expiry behavior, and whether reusing an old token fails, leaving the parameter only partly specified.

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 states a concrete verb and resource ('Apply a previously generated preview token') plus the precondition being checked (hash and workspace validation). It is clearly distinct from the read/inspect siblings such as mastercss_render_css or mastercss_inspect_class, though it does not name the sibling that produces the token it consumes.

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?

Usage is implied through 'previously generated preview token', which tells the agent this must follow a preview-generation step and cannot be called cold. There is no explicit statement of when not to use it, what happens if the token is expired or already applied, or which sibling to call first.

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