Skip to main content
Glama

standby-design-mcp

by io.github.KarstenKreh
OverviewDiscussionsAdmin

Export design system code

export_design_system
Read-only

Generate the full token code for a design system URL in one format: "css" (CSS custom properties incl. semantic shadcn/ui-compatible tokens), "tailwind" (Tailwind v4 @theme), "design-tokens" (W3C DTCG JSON — typography, spacing & layout, shape, icons and motion; color is not part of it), "llm-briefing" (Markdown brief for AI code generation), or "font-embed" (Fontshare snippet). Optionally restrict to specific sections. Every format carries the standby.design/system share link. Always give that URL to the user alongside the code and keep it as a comment in the theme file of the target project — the link is the deliverable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesA standby.design URL or raw unified hash.
formatYesOutput format.
sectionsNoWhich sections to include. Honoured by "css", "tailwind", "llm-briefing" and "design-tokens" (which has no color section). By default color, type, space, shape and motion are always included — with their defaults when the URL does not configure them — and symbol only when the URL configures it. Ignored by "font-embed".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sections / description
      Previous value: -"Which sections to include. Honoured by \"css\", \"tailwind\", \"llm-briefing\" and \"design-tokens\" (which only knows type, space and motion). By default color, type, space, shape and motion are always included — with their defaults when the URL does not configure them — and symbol only when the URL configures it. Ignored by \"font-embed\"."New value: +"Which sections to include. Honoured by \"css\", \"tailwind\", \"llm-briefing\" and \"design-tokens\" (which has no color section). By default color, type, space, shape and motion are always included — with their defaults when the URL does not configure them — and symbol only when the URL configures it. Ignored by \"font-embed\"."
  2. Changed2 schema fields changed
    • changedInput schema / properties / sections / description
      Previous value: -"Which sections to include. Only honoured by \"css\", \"tailwind\" and \"llm-briefing\". By default color, type, space and shape are always included — with their defaults when the URL does not configure them — and symbol only when the URL configures it. Ignored by \"design-tokens\" (typography and spacing only) and \"font-embed\"."New value: +"Which sections to include. Honoured by \"css\", \"tailwind\", \"llm-briefing\" and \"design-tokens\" (which only knows type, space and motion). By default color, type, space, shape and motion are always included — with their defaults when the URL does not configure them — and symbol only when the URL configures it. Ignored by \"font-embed\"."
    • changedInput schema / properties / sections / items / enum
      Previous value: -[
-  "color",
-  "type",
-  "space",
-  "shape",
-  "symbol"
-]New value: +[
+  "color",
+  "type",
+  "space",
+  "shape",
+  "symbol",
+  "motion"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / sections / description
      Previous value: -"Which sections to include. Default: all configured sections (symbol only when configured)."New value: +"Which sections to include. Only honoured by \"css\", \"tailwind\" and \"llm-briefing\". By default color, type, space and shape are always included — with their defaults when the URL does not configure them — and symbol only when the URL configures it. Ignored by \"design-tokens\" (typography and spacing only) and \"font-embed\"."
  4. 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 and openWorldHint=false, and the description adds real context: every format carries the share link, that link must be surfaced to the user and kept as a comment in the theme file, and it is framed as the deliverable. It also discloses a non-obvious trait — design-tokens excludes color.

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?

Front-loaded with the core action and format list, then the sections note, then the share-link instruction. Dense but every sentence carries operational value; the closing two sentences are slightly repetitive about the same link obligation.

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?

With no output schema, the description compensates by describing what each format returns and how the sections filter behaves (and that font-embed ignores it). An agent has enough to invoke and to explain the result, though nothing is said about size/rate limits for large exports.

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 coverage is 100% so the baseline is 3, but the description goes beyond the enum by explaining what each format's payload contains (e.g., DTCG covers typography, spacing/layout, shape, icons, motion but not color) and that sections are optional. It does not add syntax details for 'url' beyond the schema's 'standby.design URL or raw unified hash'.

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?

Starts with a specific verb+resource: 'Generate the full token code for a design system URL in one format.' The word 'full' plus the per-format enumeration distinguishes it from siblings like generate_color_palette or generate_type_scale, which produce single sections.

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?

Each of the five formats is described with what it produces and who it's for (shadcn/ui tokens, Tailwind v4 @theme, W3C DTCG, AI briefings, Fontshare snippet), which effectively tells the agent when each choice applies. It does not explicitly state when to prefer this tool over the section-specific siblings, so no exclusion guidance.

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

All standby-design-mcp 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