Skip to main content
Glama

standby-design-mcp

by io.github.KarstenKreh
OverviewDiscussionsAdmin

Generate shape tokens

generate_shape_tokens
Read-only

Generate shape tokens — radii, shadows, borders, focus rings — in one of four visual styles: "paper" (classic surfaces with layered shadows), "glass" (liquid glass), "neomorph" (soft neumorphism), "neobrutalism" (hard offset shadows). Returns a shareable standby.design/system URL and a summary. Always give that URL to the user — the link is the deliverable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoExisting standby.design URL (or raw hash) to modify. Only this tool's section is changed; color/type/shape/icon/spacing/motion settings from other tools are preserved. Omit to start fresh from defaults.
styleNoTop-level visual style (default "paper").
glassBlurNoGlass backdrop blur (default 1.0).
ringStyleNoFocus ring shape: "soft" (default) is a translucent halo at the edge plus a full-color border, "solid" is a hard outline set off by ringOffset.
ringWidthNoFocus ring width in px (default 2).
glassDepthNoGlass displacement intensity (default 0.2).
ringOffsetNoFocus ring offset in px (default 2).
shadowTypeNoShadow rendering for paper style.
borderWidthNoBorder width in px (default 1).
shadowScaleNoElevation level spread ratio (default 1.272).
borderRadiusNoBase radius in px; scales to a xs–xl radius set (default 8).
ringColorHexNoCustom focus ring color as hex, or "auto" (default).
borderEnabledNo
shadowEnabledNo
shadowOffsetXNoBrutalist shadow X offset in px (default 2).
shadowOffsetYNoBrutalist shadow Y offset in px (default 4).
borderColorHexNoCustom border color as hex, or "auto" (default).
separationModeNoHow surfaces separate from the background.
shadowColorHexNoCustom shadow color as hex, or "auto" (default).
shadowStrengthNoShadow alpha multiplier (default 1.0).
glassDispersionNoChromatic aberration intensity (default 0.5).
shadowBlurScaleNoShadow blur multiplier (default 1.0).
brutalistVariantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / glassDispersion / description
      Previous value: -"Chromatic aberration intensity (default 0.4)."New value: +"Chromatic aberration intensity (default 0.5)."
  2. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Existing standby.design URL (or raw hash) to modify. Only this tool's section is changed; color/type/shape/icon/spacing settings from other tools are preserved. Omit to start fresh from defaults."New value: +"Existing standby.design URL (or raw hash) to modify. Only this tool's section is changed; color/type/shape/icon/spacing/motion settings from other tools are preserved. Omit to start fresh from defaults."
  3. Changed1 schema field changed
    • addedInput schema / properties / ringStyle
      Added value: +{
+  "description": "Focus ring shape: \"soft\" (default) is a translucent halo at the edge plus a full-color border, \"solid\" is a hard outline set off by ringOffset.",
+  "enum": [
+    "soft",
+    "solid"
+  ],
+  "type": "string"
+}
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower. The description adds real behavioral context: it returns a shareable standby.design/system URL plus a summary, and stresses that the URL is the deliverable and must be surfaced to the user. It does not, however, describe how the modify-existing-URL flow behaves in prose (the schema carries that).

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?

Three sentences that are front-loaded with the verb and resource, followed by return behavior and the critical hand-off instruction. The style list is slightly dense but each parenthetical carries distinct meaning, and nothing is filler.

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?

For a 23-parameter tool with no output schema, the description covers the essentials: what it generates, the style taxonomy, and what it returns. It is nearly complete, missing only routing guidance among the sibling generator/token tools.

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 87%, so the baseline is 3. The description earns an extra point by going beyond the bare enum and explaining what each style means ('paper' = layered shadows, 'glass' = liquid glass, 'neomorph' = soft neumorphism, 'neobrutalism' = hard offset shadows), which is genuine semantic value for the most important parameter.

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 (Generate) and resource (shape tokens) and enumerates the sub-resources it covers — radii, shadows, borders, focus rings. The four named styles further distinguish it from siblings like generate_color_palette or generate_type_scale without needing to open any schema.

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 description tells the agent what to do with the result ('Always give that URL to the user') but never says when to choose this tool versus siblings such as get_design_system or generate_space_tokens. Usage is only implied by the token category in the name.

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