Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Suggest Master CSS Syntax

mastercss_suggest_syntax
Read-onlyIdempotent

Get language-service completions and hover context at a given document position to resolve Master CSS syntax and speed up editing.

Instructions

Return language-service completions and hover context for a document position.

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": {
      "content": "<content>",
      "filePath": "<filePath>",
      "position": "<position>"
    },
    "name": "mastercss_suggest_syntax"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
contentYes
contextNo
filePathYes
positionYes
triggerCharacterNo

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 readOnly, idempotent, non-destructive, and closed-world, so safety needs no restating. The description adds real context by revealing the tool serves two modes (completions and hover context), but it never says what selects between those modes, nor mentions the limit ceiling or the project/preset context switch that visibly affect output.

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?

One tight sentence with the action and scope front-loaded and zero filler. It is arguably too compressed for a six-parameter tool, but nothing in the sentence 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?

For a tool with a nested position object, an enum, a trigger character, and 0% schema coverage, this single sentence leaves too much for the agent to guess, especially the project-vs-preset context and what triggerCharacter does. The existence of an output schema excuses it from explaining return values, but the input-side gaps remain substantial.

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, so the description must carry the explanatory load and it largely does not. Only "document position" maps to a parameter; content, filePath, limit, context (project vs preset), and triggerCharacter — the last of which likely drives the completion/hover behavior — are left 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 gives a concrete verb ("Return") and a specific resource pair ("language-service completions and hover context") scoped to "a document position", so an agent can tell this is an editor-style lookup. It does not, however, contrast itself with the closely related mastercss_suggest_classes sibling, leaving the boundary to inference.

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 when-to-use / when-not-to-use guidance and no named alternative, even though mastercss_suggest_classes sits right next to it in the catalog. The only implicit cue is "for a document position", which hints at editor/cursor-driven usage but states no condition or prerequisite.

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