Skip to main content
Glama

standby-design-mcp

by io.github.KarstenKreh

Generate spacing & layout tokens

generate_space_tokens
Read-only

Generate spacing tokens (3xs–3xl), breakpoints, container widths, prose measure, and aspect ratios. 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 settings from other tools are preserved. Omit to start fresh from defaults.
modeNo"harmonic": multiples of the base (default). "geometric": compound ratio steps.
snapNoSnap token values to a sensible grid (default true).
ratioNoRatio for geometric mode (default 1.272).
baseRemNoBase spacing in rem (default 1.0).
containersNoReplace the container list. Defaults: prose 680, narrow 960, default 1200, wide 1440, full 1920.
fluidMaxVwNoUpper fluid viewport anchor in px (default 1920).
fluidMinVwNoLower fluid viewport anchor in px (default 375).
multiplierNoUniform scale factor on all tokens (default 1.0).
proseMaxChNoProse measure in ch (default 65).
breakpointsNoReplace the breakpoint list, e.g. [{"name":"sm","minPx":640},...]. Defaults: sm 640, md 768, lg 1024, xl 1280, 2xl 1536.
aspectRatiosNoReplace the aspect ratio list, e.g. [{"name":"video","w":16,"h":9}].
includeReciprocalsNoAlso export flipped (portrait) variants of each ratio (default true).

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint=true and openWorldHint=false provided, the safety profile is covered. The description adds valuable behavioral context by revealing the return format (shareable URL and summary) and the critical instruction that the URL is the deliverable the agent must provide to the user. No contradictions with annotations.

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?

The description is two sentences long: the first states exactly what the tool generates, the second explains the deliverable and required user-facing action. No wasted words, and the most important information is front-loaded.

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?

Given the 13-parameter complexity and no output schema, the description adequately communicates the return value (URL and summary) and the user-facing requirement. It could additionally mention that an existing URL is modified, but that information is already in the schema, so the description is sufficiently complete.

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% with all 13 parameters documented in the schema. The main description does not add parameter-level detail beyond the schema, so baseline 3 is appropriate.

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 clearly states a specific verb ('Generate') and resource ('spacing tokens'), enumerating the exact output categories (3xs–3xl, breakpoints, container widths, prose measure, aspect ratios). It distinguishes itself from sibling token generators like generate_color_palette and generate_type_scale.

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?

The description clearly implies use for generating spacing/layout tokens, and the sibling tool names make the alternative tools obvious. However, it does not explicitly say when not to use this tool or name alternatives directly, so it stops short of a 5.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct design token category (color, icon, shape, space, type) or a distinct operation (export, get, list fonts). There is no overlap in purpose or output format.

Naming Consistency5/5

Generation tools consistently use generate_*_tokens except for generate_type_scale and generate_color_palette which still follow the generate_ verb. Utility tools use clear action verbs (export, get, list) with all lowercase snake_case naming.

Tool Count5/5

Eight tools provide a well-scoped set for design system token generation and retrieval. Each tool earns its place without redundancy or unnecessary bloat.

Completeness4/5

The set covers the main design system pillars (color, typography, spacing, shape, icons) plus export and retrieval workflows. Minor gaps like a direct 'update' or 'delete' tool are unnecessary for the generative use case.

Resources