Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Preview Master CSS Directive Format

mastercss_preview_directive_format

Preview formatting for Master CSS directives safely or format in-memory content without writing files, so you can validate directive changes before applying edits.

Instructions

Create a safe preview for formatting Master CSS directives, or format in-memory content without writing files.

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

Input Schema

NameRequiredDescriptionDefault
rangeNo
ttlMsNo
contentNo
contextNo
filePathNo
patternsNo

Output Schema

NameRequiredDescriptionDefault
resultYes
versionYes
metadataYes
diagnosticsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.1/5.0
Behavior3/5

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

The description adds real context beyond the annotations by promising a 'safe' operation that does not write files, which offsets the readOnlyHint=false hint that some state is still created. It does not explain what that state is, how long a preview lives (the ttlMs parameter strongly implies an expiring preview session), or what happens on repeat calls despite idempotentHint=false.

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 compact sentence with the core action front-loaded and no filler. The 'or' clause is slightly ambiguous in how the two modes relate, but nothing is wasted.

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 described, but this is a six-parameter tool with a nested range object and zero schema coverage. Key semantics that determine correct invocation — what range selects, what ttlMs governs, when context should be project versus preset, whether filePath is required for the preview mode — are absent.

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 six parameters, including a nested range object and a project/preset enum, so the description carries the full explanatory burden and largely fails. It only obliquely touches 'content' via 'in-memory content' and 'filePath' via 'without writing files', leaving range, ttlMs, context, and patterns entirely undefined.

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 and resource: it creates a preview of Master CSS directive formatting, and can also format in-memory content. The 'without writing files' clause hints at the boundary with write-oriented siblings such as mastercss_apply_preview, but no sibling is named, so the distinction stays partial.

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 only implied: the agent can infer this is the tool for inspecting a formatting result before committing it, or for formatting a string without touching disk. There is no explicit 'use this when… instead of…' statement and no named alternative, leaving routing decisions to inference.

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