Skip to main content
Glama

Extract Design System

extract_design_system
Read-onlyIdempotent

Extract colors, typography, and spacing tokens from CSS or HTML into a design system to standardize styles and reuse consistent UI tokens.

Instructions

Extract colors, typography and spacing tokens from CSS or HTML into a design system.

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": {
      "source": "<source>"
    },
    "name": "extract_design_system"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesCSS/HTML source or description
appNameNoName of the app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is fully covered by structured data. The description adds nothing beyond that: it does not say what the resulting 'design system' looks like, whether partial extraction is possible, or what happens with malformed input. For a tool with no output schema, some return-shape context would have been valuable.

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?

A single tight sentence with the verb front-loaded and zero filler. It is efficient, though the brevity comes at the cost of the usage and output detail noted elsewhere; nothing in it is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple two-parameter, non-destructive read tool with full schema coverage and rich annotations, so the description is close to sufficient. The gap is the output: with no output schema, an agent gets no signal about what the extracted 'design system' contains or how it is structured.

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 source and appName are already documented in the schema, and the description does not add format, syntax, or default information. The mention of 'CSS or HTML' only loosely echoes the schema's 'CSS/HTML source or description'. Baseline 3 is appropriate when the schema does the heavy lifting.

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 uses a specific verb and resource: extract colors, typography and spacing tokens from CSS or HTML. It scopes what is extracted, so an agent knows it is a token-extraction tool rather than a general analyzer. It does not name or distinguish itself from the nearest sibling, html_css_to_javafx_css, which also consumes CSS/HTML.

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 explicit guidance on when to use this tool, when not to, or which sibling to prefer. The phrase 'from CSS or HTML' implies the input precondition but does not state whether it works on a file path, raw source text, or a prose description, nor does it route the agent away from the conversion siblings.

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