Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Extract Master CSS Classes

mastercss_extract_classes
Read-onlyIdempotent

Extract class positions and validation summaries from project files or an in-memory source buffer to locate and verify Master CSS class usage.

Instructions

Extract class positions and validation summaries from project files or an in-memory source buffer.

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

Input Schema

NameRequiredDescriptionDefault
contentNo
contextNo
filePathNo
patternsNo
includeRulesNo

Output Schema

NameRequiredDescriptionDefault
resultYes
versionYes
metadataYes
diagnosticsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so safety is covered. The description adds that input may come from project files or an in-memory buffer, which is useful behavioral context, but it says nothing about how project scanning behaves (scope, cost, what files are touched).

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 the verb first and no filler. It is appropriately sized for the purpose statement, though brevity here reflects omission rather than efficiency in covering parameters.

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?

For a five-parameter tool with zero schema description coverage, the description leaves key inputs (patterns, includeRules, context disambiguation) undocumented. The output schema removes the need to explain return values, but the input side remains substantially underspecified.

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 optional parameters, so the description carries the full burden yet names none of them. It loosely maps "in-memory source buffer" to content and "project files" to context/filePath, but patterns and includeRules are left entirely unexplained.

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?

Uses a specific verb ("Extract") with a named resource ("class positions and validation summaries") and states the two source modes, so the agent knows the operation. It does not differentiate from siblings such as mastercss_trace_class or mastercss_scan_project, which overlap in domain.

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?

Implies two usage modes (project files vs in-memory buffer) but never states when to choose one over the other, nor points to any alternative sibling for adjacent tasks. An agent must infer the selection rule from the context enum alone.

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