Skip to main content
Glama

CSS Crème

by com.csscreme
OverviewDiscussionsAdmin

Measure a design system across a whole site, not one page

decode_site
Read-onlyIdempotent

Read a sample of pages from one site (from its sitemap.xml, or the homepage links when there is no sitemap) and report what is CONSISTENT across them: which declared tokens, colours, font stacks, radii and spacing values appear on every page read, and which appear on only some. One page shows what a page uses; a design system is a claim about consistency, and only a sample can test it. Returns counts and the pages actually read, never a score. Use when the user asks whether a site is really on a system, or wants the system rather than one page of it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAbsolute public http(s) URL anywhere on the site.
pagesNoHow many pages to read, 2 to 8. Default 5.
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?

Beyond the readOnly/idempotent annotations, the description reveals how the tool behaves: it reads from sitemap.xml or homepage links, samples multiple pages, reports consistency counts, and 'never a score.' This adds real process-level context that annotations alone do not provide, without contradicting them.

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?

Three dense sentences cover method, fallback behavior, what is reported, what is not reported, and the intended use case. No sentence is filler, and the most decision-relevant information is front-loaded.

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?

Given rich annotations and a fully documented schema, the description still supplies the missing conceptual context: what 'design system' means operationally, how sampling works, and exactly what the output does and does not contain. An agent has enough to decide when to call it and what to expect, even with no output schema.

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?

The input schema already documents all three parameters at 100% coverage, including defaults and cache semantics. The description reinforces the sampling and consistency concepts but does not add parameter-specific meaning beyond what the schema provides, so the baseline of 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 names a specific verb and resource: 'Read a sample of pages from one site' and 'report what is CONSISTENT across them.' The title and closing contrast with 'not one page' clearly distinguish this from page-level tools like decode_url or get_design_md_for_url, so sibling confusion is unlikely.

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

Usage Guidelines4/5

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

The description gives an explicit trigger: 'Use when the user asks whether a site is really on a system, or wants the system rather than one page of it.' It does not name specific alternative tools or state when not to use it, but the 'rather than one page' phrasing implies the boundary clearly enough.

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