Better Design

Get Design System Generation Status

get-design-system-status

Read-onlyIdempotent

Track design system generation progress started with create-design-system. Returns live status, preview URL, and the npx shadcn add install command once complete.

Instructions

Check on a design system generation started with 'create-design-system'. Returns progress while generating, and the live preview URL + the npx shadcn add install command once complete. Generation typically takes 1-3 minutes; poll every ~30 seconds until it reports ready. Once ready, ask the user what's next (icon library, install, or build) instead of stopping.

Input Schema

Name	Required	Description	Default
`context`	No	Optional. One sentence on WHY you are calling this and what the user asked for (e.g. 'adding nav icons for the fintech dashboard'). Used only for usage analytics; does not change the result.
`projectId`	Yes	The project id returned by create-design-system.

Output Schema

Name	Required	Description
`name`	Yes	Display name of the design system or project.
`step`	No	Current generation step, while generating.
`status`	Yes	completed \| error \| pending \| generating \| selected
`shotUrl`	No	Real screenshot of the showcase page for the self-contained preview widget.
`viewUrl`	No	Owner-facing Better Design page (the human 'Open' link). May require login.
`tokensCss`	Yes	CSS custom-property stylesheet for the system's tokens.
`previewUrl`	No	Public, cookieless showcase URL used to generate preview assets. Falls back to viewUrl.
`installNote`	No	Important install flavor or fallback note for clients that read only structuredContent.
`installedTo`	No	The project folder this server installed the design system into. Build there; run no setup command.
`localInstall`	No	True when this server runs on the user's machine and installs the design system itself: call get-design-system-kit again with install: true.
`installCommand`	No	shadcn install command, when complete.
`installLibrary`	No	Actual component library flavor installed by installCommand.
`buildInstructions`	No	Required design-choice guidance and any target-specific build/review steps for clients that read only structuredContent.
`newProjectCommand`	No	Creates a Vite + React + TypeScript project with Tailwind v4, the @/* alias and components.json, for when there is no project yet. Run it, then run installCommand inside the new my-app folder.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint, so the safety profile is covered; the description adds genuinely new behavior: the 1-3 minute duration, the two distinct response phases (progress vs. ready with preview URL and install command), and the recommended polling loop. This is exactly the operational context annotations cannot convey.

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?

Four short sentences, front-loaded with the core purpose and then layering timing, polling, and the post-ready handoff. Every sentence carries actionable information with no repetition of the schema.

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?

An output schema exists, yet the description still names the key return payload (preview URL, `npx shadcn add` command) at a level that supports decision-making, and it covers the async lifecycle an agent needs to call this correctly. Nothing required to invoke or interpret it is missing.

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% and both parameters are documented in-schema, including that projectId comes from create-design-system and that context is analytics-only. The description adds no syntax or format meaning beyond that, so the baseline of 3 applies.

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 ('Check on') and resource ('design system generation'), and explicitly ties it to the sibling that starts the job ('create-design-system'). It also distinguishes polling-in-progress from the completed-state output, so an agent can tell this apart from create-design-system without opening either 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?

Gives explicit when-to-use (poll while generating), a concrete cadence ('every ~30 seconds'), the alternative tool that initiates the operation, and even post-completion behavior ('ask the user what's next ... instead of stopping'). Nothing about routing or timing 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.

Deploy Server