Skip to main content
Glama

Generate Design System

generate_design_system

Generate a complete starter design system from a brand color and mood, including color scales, semantic themes, typography, spacing, radii, shadows, and contrast checks.

Instructions

One call, a complete starter design system from a brand color and a mood: color scales, light and dark semantic themes, font pairing, fluid type scale, spacing, radii, layered shadows, base styles, and verified contrast checks. Deterministic, no API key needed.

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": {
      "brand": "<brand>"
    },
    "name": "generate_design_system"
  }
}

Input Schema

NameRequiredDescriptionDefault
moodNoDrives the font pairingmodern
brandYesBrand color as hex, e.g. #e11d48
formatNocss
radiusNosoft
harmonyNoanalogous
type_ratioNomajor-third
shadow_styleNosoft
spacing_baseNo
base_font_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses determinism, that no API key is required, and that contrast checks are verified rather than assumed — solid traits. However, it never says whether output is returned inline as CSS/JSON text versus written somewhere, nor anything about output size or how the long parameter set changes the result, which is a material gap for a 9-parameter generator.

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?

It is a single front-loaded sentence that leads with the value proposition ('One call, a complete starter design system') before enumerating outputs, with no filler. The output enumeration is long but each item conveys real scope information rather than repetition.

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?

With no output schema and nine parameters at 22% description coverage, the definition should say more about the returned artifact and how the tuning parameters shape it. The output enumeration partly compensates by telling the agent what will be produced, but the parameter behavior and return shape remain underspecified.

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

Parameters2/5

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

Schema description coverage is only 22%, so the description must compensate and largely does not. Beyond noting that brand color and mood are the inputs, it explains none of the seven other parameters (harmony, radius, type_ratio, spacing_base, base_font_size, shadow_style, format) and does not state how, for example, harmony or type_ratio alter the generated scales.

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 specific verb and a precisely scoped resource: a complete starter design system generated from a brand color and mood. It enumerates the full output bundle (color scales, semantic themes, fonts, type scale, spacing, radii, shadows, base styles, contrast checks), which implicitly distinguishes it from the many narrower sibling generators like generate_palette, generate_type_scale, and generate_shadows.

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

Usage Guidelines3/5

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

The word 'starter' implies greenfield bootstrap usage, and 'one call' implies it replaces composing several single-purpose generators, but neither is stated explicitly. No sibling is named, no when-not guidance is given, and there is no mention of when an agent should instead call generate_dark_theme or suggest_font_pairings for a narrower need.

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