Skip to main content
Glama

Better Design

by io.github.marvkr
OverviewDiscussionsAdmin

Set a Project's Design Config

set-design-config
DestructiveIdempotent

Saves exact design token values (colors, radius, fonts, icon library and layout density) onto a generated project, merged over its current config. The saved values replace the earlier ones, and anyone with the project's config URL can read them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
configYesPartial design config to merge over the current one. Only pass the fields the user changed. Colors are oklch() strings (e.g. 'oklch(0.62 0.11 45)'); radius is a CSS length (e.g. '0.75rem'); fonts are family names; density is compact, comfortable or spacious and overrides the design system's layout density.
projectIdYesThe project id returned by create-design-system.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / config / description
      Previous value: -"Partial design config to merge over the current one. Only pass the fields the user changed. Colors are oklch() strings (e.g. 'oklch(0.62 0.11 45)'); radius is a CSS length (e.g. '0.75rem'); fonts are family names."New value: +"Partial design config to merge over the current one. Only pass the fields the user changed. Colors are oklch() strings (e.g. 'oklch(0.62 0.11 45)'); radius is a CSS length (e.g. '0.75rem'); fonts are family names; density is compact, comfortable or spacious and overrides the design system's layout density."
    • addedInput schema / properties / config / properties / density
      Added value: +{
+  "enum": [
+    "compact",
+    "comfortable",
+    "spacious"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true. The description adds genuinely useful context beyond them: the merge-over-current semantics, that saved values overwrite earlier ones, and that anyone with the config URL can read them.

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?

Two tightly written sentences, front-loaded with the action and resource, followed by merge/visibility semantics. No wasted clauses, though the second sentence combines two ideas.

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?

No output schema exists, so return values need not be explained. For a 2-param write with 100% schema coverage and rich annotations, the merge/overwrite behavior and read-visibility note make it nearly complete; only explicit sibling routing 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 the schema already documents each config field with examples (oklch strings, rem radius, density enum). The description restates the same field groups, so the 3 baseline is appropriate with the schema carrying the load.

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 (Saves) and resource (exact design token values) plus the target (a generated project) and the fields touched (colors, radius, fonts, icon library, layout density). It is clearly the write counterpart to the read-only get-design-config sibling, and the merge wording further pins down its role.

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?

Usage is implied by 'merged over its current config' and 'saved values replace the earlier ones', which tells the agent this is a partial-update write. However, it names no alternative and gives no explicit when-to-use/when-not guidance (e.g. vs create-design-system or get-design-config).

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

All Better Design 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