Skip to main content
Glama

sync_design_tokens

Map design tokens from local registry to a Tailwind config theme extension object. Returns a ready-to-merge partial Tailwind theme with CSS variable references.

Instructions

Map design system tokens from the local registry to a Tailwind config theme extension object.

Prerequisites: Tokens must already be in the local registry (run pull_design_system or get_tokens to verify). No Figma connection required.

Returns on success: A partial Tailwind theme object ready to merge into tailwind.config.ts under theme.extend, e.g. { colors: { primary: "var(--colors-primary)", ... }, spacing: { xs: "var(--spacing-xs)", ... }, fontSize: {...}, borderRadius: {...}, boxShadow: {...} }. Empty token categories are omitted. Token keys are derived from the last segment of the token name, lowercased and hyphenated. CSS variables are preferred over raw values when available.

Error behavior: Never throws — returns an empty object {} if no tokens are in the registry.

Use this tool vs get_tokens: get_tokens returns raw token data for inspection; sync_design_tokens returns a Tailwind-ready patch you can directly paste into your config. Tokens of type "other" are skipped as they have no standard Tailwind mapping.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses behavior: return structure, key derivation, CSS variable preference, empty category omission, error behavior (never throws, returns empty object), and skipped token types. This is comprehensive.

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 well-structured and concise. Each sentence serves a purpose: purpose, prerequisites, return details, error handling, comparison. No unnecessary words.

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?

Given no output schema and no annotations, the description covers all necessary context: return value, prerequisites, error behavior, and token handling. It is complete for an agent to select and invoke correctly.

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?

The input schema has zero parameters, so baseline is 4. The description adds no parameter info (none needed), but explains the output and behavior in detail, compensating for lack of parameters.

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 the tool's purpose: mapping design tokens to a Tailwind config theme extension. The verb 'map' and resource 'design tokens to Tailwind config' are specific, and it distinguishes from siblings like get_tokens and update_token.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit prerequisites are given (tokens must be in registry), and an alternative tool (get_tokens) is compared for when raw data is needed. The description also clarifies that no Figma connection is needed, guiding proper usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sarveshsea/memi'

If you have feedback or need assistance with the MCP directory API, please join our Discord server