Skip to main content
Glama

Designesy

by io.github.LE-VAI
OverviewDiscussionsAdmin

designesy_monitor_score

Score a URL for continuous design-drift governance, the temporal layer over the drift radar. Re-runs the 12 drift checks (d01-d12) on the URL and computes 10 monitor checks (m01-m10): schedule registered, last run fresh, drift delta vs baseline, trend slope (3-run trajectory), new violations since last run, resolved since last run (the healing signal), score degradation threshold, token-set mutation, contract version drift, and alert delivered. When alerts fire and an email address is provided, sends an HTML drift-alert email via Resend (requires RESEND_API_KEY env var). Pass a history array of prior snapshots to compute deltas; omit it for a first-run baseline. Use this to watch a design system over time: "weekly audits at cents per report" (Into Design Systems 2026). When NOT to use: for a single point-in-time drift check, use designesy_drift_score; for design-contract scoring, use designesy_score. Executable: fetches the URL, extracts CSS + :root tokens, runs checks, computes deltas. No browser needed. Returns JSON: { ok, url, score (0-100, governance health), grade (A-F), pass, warn, fail, total, currentSnapshot, baseline, previous, driftChecks, monitorChecks, alerts, emailAlert }. Results cached ~24h per URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to monitor for drift. Defaults to https://www.designesy.org/ if not provided.
emailNoEmail address to receive drift alerts. When alerts fire AND this is provided AND RESEND_API_KEY is set, an HTML alert email is sent. Optional: without it, alerts surface in-UI only.
historyNoPrior snapshots for delta computation. Omit for a first-run baseline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"Email address to receive drift alerts. When alerts fire AND this is provided AND RESEND_API_KEY is set, an HTML alert email is sent. Optional — without it, alerts surface in-UI only."New value: +"Email address to receive drift alerts. When alerts fire AND this is provided AND RESEND_API_KEY is set, an HTML alert email is sent. Optional: without it, alerts surface in-UI only."
  2. Changed1 schema field changed
    • addedInput schema / properties / email
      Added value: +{
+  "description": "Email address to receive drift alerts. When alerts fire AND this is provided AND RESEND_API_KEY is set, an HTML alert email is sent. Optional — without it, alerts surface in-UI only.",
+  "type": "string"
+}
  3. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / history / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / history / items / properties / checks / items / additionalProperties
      Removed value: -false
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and meets it: it discloses that an HTML alert email is sent via Resend (requiring RESEND_API_KEY), that it is executable (fetches URL, extracts CSS + :root tokens, computes deltas, no browser), that results are cached ~24h per URL, and it lists the return JSON fields. Effects, dependencies, and side effects are all surfaced.

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 definition is dense and long, but it is front-loaded with the core purpose and the check inventory before routing rules and return shape. The 'when NOT to use' and return JSON are separated into clear segments. Slightly over-packed with check IDs and marketing quote, but every segment earns its place.

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?

For a 3-param, no-annotation, no-output-schema executable tool with external dependencies, the description is complete: it covers inputs, execution model, alert side effects, caching, and the return field list, which substitutes for the missing output schema. An agent has everything needed to call it correctly or route elsewhere.

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?

Schema description coverage is 100%, so the schema already documents all three params, giving a baseline of 3. The description adds genuine meaning beyond the schema: it explains the history array as prior snapshots for delta computation and the omit-for-baseline behavior, and clarifies the email/alert trigger chain (alerts fire AND email provided AND RESEND_API_KEY set). This is useful semantics layered on top of complete schema docs.

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?

States a specific verb+resource ('Score a URL for continuous design-drift governance') and frames the tool's role as 'the temporal layer over the drift radar.' It enumerates the concrete work (12 drift checks d01-d12, 10 monitor checks m01-m10) and names the exact sibling alternatives, so an agent can distinguish it from designesy_drift_score and designesy_score without opening any schema.

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?

Provides explicit when-to-use ('watch a design system over time'), an operational rule for the history param ('Pass a history array ... omit it for a first-run baseline'), and an explicit 'When NOT to use' clause naming two alternatives by name with the condition that selects each. Nothing about tool selection is left to inference.

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

All Designesy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources