Skip to main content
Glama

standby-design-mcp

by io.github.KarstenKreh

Inspect design system

get_design_system
Read-only

Decode a standby.design URL (or raw hash) and return an overview of the full design system: color palette, type scale, spacing & layout, shape tokens, and icons — plus per-tool edit links. Always give the standby.design/system URL to the user — the link is the deliverable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesA standby.design URL or raw unified hash (e.g. from a previous generate_* call or copied from the browser).

TDQS

A4.6/5.0
Behavior4/5

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

Consistent with readOnlyHint=true (no modification). Adds useful details about output structure (overview content, per-tool edit links) and states the URL is the deliverable, beyond what annotations provide.

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?

Two sentences, no wasted words. First sentence explains purpose and output. Second sentence gives a key usage instruction. Front-loaded and efficient.

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?

For a single-parameter tool with no output schema, the description sets complete expectations: input format, output components, and usage instruction. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning beyond schema: clarifies acceptable input types (standby.design URL or raw hash) and provenance (from generate_* calls or browser). Schema has 100% coverage but description enriches understanding.

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?

Describes decoding a standby.design URL/hash and returning a full design system overview. Clear verb 'decode' and resource 'design system overview'. Distinguishes from sibling generation tools by focusing on inspection.

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?

Implies use when a URL/hash is available for inspection. Includes explicit instruction to give the URL to the user as the deliverable. Does not explicitly state when not to use, but context with siblings makes it clear.

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