Skip to main content
Glama

CSS Crème

by com.csscreme
OverviewDiscussionsAdmin

Get a complete DESIGN.md for any public URL

get_design_md_for_url
Read-onlyIdempotent

Read the stylesheets of a public site and return a full DESIGN.md: semantic roles with the token each came from, measured WCAG contrast pairs, the tokens the site itself declares (framework internals counted separately), font families, the type scale with the ratio between steps, colour frequency, gradients, corner radii, spacing, an elevation ladder of shadows, breakpoints, the z-index ladder, interaction-state rule counts, motion, and whether a dark theme is declared. This is the artefact to hand a coding agent before it writes UI that should match a site. It reads declared CSS and does not execute JavaScript, so it reports what the stylesheets say rather than what the page renders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAbsolute public http(s) URL of the page to read.
maxAgeNoHow old a reused read may be, in seconds. Default 600; 0 reads the site now. A reused read keeps its own fetchedAt and says cache.hit: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / maxAge
      Added value: +{
+  "description": "How old a reused read may be, in seconds. Default 600; 0 reads the site now. A reused read keeps its own fetchedAt and says cache.hit: true.",
+  "maximum": 3600,
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context: it reads declared CSS, does not execute JavaScript, and reports what stylesheets say rather than what the page renders. This goes beyond annotations, though it could disclose failure modes like unreachable URLs or non-CSS sites.

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?

The description is a single dense paragraph that front-loads the core action and lists the output contents. Every sentence earns its place, but the long enumeration could be more scannable with bullet points or short labeled sections. It is appropriately sized given the tool's complexity.

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?

Given the rich description and full schema coverage, the tool is well specified. With no output schema, the description explains return values in detail by listing DESIGN.md contents. The only gaps are edge-case behaviors such as failure modes for unreachable URLs or pages that require JavaScript, which an agent might need to handle.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already fully documented in the schema. The description reinforces the URL semantics and mentions cache behavior for maxAge, but it does not add substantial meaning beyond the structured schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a precise verb+resource ('Read the stylesheets of a public site and return a full DESIGN.md') and enumerates the artifact's contents in detail. It clearly distinguishes itself from siblings by specifying the full-design-md scope and the 'any public URL' target.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use this tool: 'This is the artefact to hand a coding agent before it writes UI that should match a site.' It also contrasts with JavaScript rendering behavior, implying when this tool is not sufficient. Sibling names like get_design_md, get_theme_tokens, and verify_design_md provide additional context for choosing alternatives.

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

All CSS Crème toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources