Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Audit Master CSS Setup

mastercss_setup_audit
Read-onlyIdempotent

Audit a workspace's Master CSS setup by checking package, entry stylesheet, manifest, integration, and package-resolution configuration in one run.

Instructions

Audit package, entry stylesheet, manifest, integration, and package-resolution setup for a workspace.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes
versionYes
metadataYes
diagnosticsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.5/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 openWorldHint=false, so the safety profile is fully covered upstream. The description adds value by enumerating the five setup areas inspected, telling the agent the scope of the sweep, but says nothing about how findings surface (error vs. report) or what a clean versus failing setup looks like.

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 sentence with the verb front-loaded and no filler; every element in the enumeration earns its place as a stated audit target. The list is slightly dense to parse ('package-resolution setup' stacks modifiers), but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, a rich annotation set, and an output schema to describe results, the description only needs to convey scope — which it does by naming all five audited areas. An agent has enough to decide whether to call it and what it covers.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not muddy this with spurious argument talk.

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 pairs a specific verb ('Audit') with an enumerated resource set (package, entry stylesheet, manifest, integration, package-resolution) scoped to a workspace, so the agent knows exactly what is being checked. It stops short of explicitly differentiating itself from adjacent siblings such as mastercss_lint_project or mastercss_workspace_info, which also operate on a project/workspace.

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 statement of when to reach for this audit versus mastercss_lint_project, mastercss_scan_project, or mastercss_workspace_info, and no prerequisites or preconditions are given. Use is only inferable from the purpose statement, not guided.

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