Skip to main content
Glama

stitch_sync_design_system

Exports OKLCH themes and design rules into Stitch-compliant DESIGN.md and .stitch/design-system.json for automated visual canvas synchronization.

Instructions

Export the current or chosen OKLCH theme and design rules into a Stitch-compliant DESIGN.md and .stitch/design-system.json for automated visual canvas synchronization.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stitch_sync_design_system"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoDesign style (e.g. 'awwwards', 'minimal', 'glass')
targetDirNoTarget repository directory (defaults to current working directory)
themeNameNoTheme name (e.g. 'Obsidian Kinetic', 'Manifesto', 'Studio')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses that this is an export that writes two named files into a target directory and exists to enable automated canvas synchronization. It does not disclose whether existing DESIGN.md or design-system.json files are overwritten, what permissions or setup are needed, or what the result looks like on success/failure.

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?

A single well-formed sentence with the verb and output artifacts front-loaded and no filler. It is dense but every clause carries information; a short second sentence on overwrite behavior would have been justified, but nothing present is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-optional-parameter export tool with no annotations and no output schema, the description covers what is produced and why, which is the core need. It is still incomplete on side effects (file overwrite, directory creation) and on how the emitted files relate to downstream Stitch operations.

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%, so the baseline is 3. The description adds only marginal meaning beyond the schema — that themeName selects an existing theme and that a 'current' theme is used when none is given — while style and targetDir are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Export) and specific resources (the current or chosen OKLCH theme and design rules), plus the exact artifacts produced: DESIGN.md and .stitch/design-system.json. An agent can distinguish this from stitch_create or design_tokens, though the description never names a sibling to contrast with explicitly.

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 phrase 'current or chosen' implies a default-versus-explicit mode, giving some context for when to call it. However, there is no explicit when-to-use guidance versus related tools such as design_tokens, generate_rules, or stitch_create, and no prerequisites or exclusions are stated.

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