Skip to main content
Glama
Master CSS MCP

Master CSS MCP

Official

Master CSS Workspace Info

mastercss_workspace_info
Read-onlyIdempotent

Reports workspace roots, resolved Master CSS packages, and project manifest status so you can verify project setup and dependencies.

Instructions

Report workspace roots, resolved Master CSS packages, and project manifest status.

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

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?

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered structurally, and an output schema exists so return shape need not be explained. The description adds only the content scope (which three things get reported); it does not mention cost, caching, or whether an unconfigured workspace yields an error versus partial results — which matters for a diagnostic tool an agent may call defensively.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler, and the resource list is front-loaded so the agent learns the scope immediately. Nothing in it could be cut without losing information.

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?

For a zero-argument, read-only tool with a full output schema and rich annotations, the description is nearly complete — the agent knows exactly what categories of information come back. The one gap is that it never says when this is the right first call versus mastercss_manifest_query or mastercss_scan_project.

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 nothing for the description to disambiguate and the baseline of 4 applies. The description correctly does not waste words on argument details.

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 ('Report') plus three concrete resources it returns: workspace roots, resolved Master CSS packages, and project manifest status. That is far more specific than a restatement of the title, but it never distinguishes itself from siblings like mastercss_manifest_query or mastercss_scan_project, which an agent could plausibly reach for instead.

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 guidance at all: no statement of context (e.g. 'use this first to understand the project layout'), no exclusions, and no named alternative. The overlap with mastercss_manifest_query is left entirely for the agent to guess at from names alone.

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