Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Query Master CSS Manifest

mastercss_manifest_query
Read-onlyIdempotent

Query active Master CSS manifest entries—tokens, utilities, mixins, custom media, containers, and token families—to inspect project or preset resources by kind, namespace, and search term.

Instructions

Query active manifest tokens, utilities, mixins, custom media, custom containers, and token families.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
queryNo
contextNo
namespaceNo

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds only the 'active manifest' scoping nuance, which tells the agent it is reading live state rather than a preset source. It says nothing about ordering, pagination with the 500 cap, or how project vs preset context affects results.

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 resource name leads. It is efficient, though the comma-separated enumeration substitutes for structure that could have grouped kinds against parameters.

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

Completeness4/5

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

Scored against a 5-parameter tool with zero schema descriptions, the description leaves real gaps: the meaning of `context` (project vs preset), what `query` matches against, and what `limit` does are all unexplained. An output schema exists, so return values need not be described. This is a notable shortfall for a tool whose parameters are otherwise opaque.

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%, so the description carries the full burden, and it only partially meets it: the listed item types loosely correspond to the `kind` enum values. The `query`, `limit`, `namespace`, and especially `context` (project vs preset) parameters get no explanation anywhere, leaving four of five parameters undocumented. The one thing it does add is the vocabulary of valid kind values, which is genuine but insufficient.

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 ('Query') with a specific resource ('manifest') and enumerates the item types returned: tokens, utilities, mixins, custom media, custom containers, and token families. An agent can distinguish this read-only lookup from siblings like inspect_class or scan_project. It stops short of explicitly contrasting itself with any named alternative, so it lands at 4 rather than 5.

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 use this tool versus alternatives, no prerequisites, and no indication of what a query without a `kind` returns. The one implicit hint is the word 'active', which suggests it covers only active manifest entries, but no condition selects this tool over the inspection or scan siblings.

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