Skip to main content
Glama
KasayoDotCom

Identity Forge MCP

Official

Get design tokens for a theme

get_tokens

Fetch design tokens for a kit in DTCG, CSS, Tailwind, or shadcn format, covering semantic colors, typography, and spacing to integrate into your existing styling layer.

Instructions

Fetch one design kit's machine-readable tokens in the format that matches the target stack. It covers all 28 semantic color roles in both light and dark, plus typography and spacing. Use it to wire a kit into an existing styling layer when you do not need the written brief; pair it with get_design_md when you also need the rules. Read-only: it returns the file contents as text and writes nothing to disk. apply_theme writes tokens and DESIGN.md into a project in one step. Free kits are public; a Pro kit returns 403 unless the key is entitled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesPermanent id or slug of the kit, from list_themes / search_themes. Prefer the id: it never moves, while a slug can be renamed and a retired slug keeps resolving through an alias.
formatNoToken format, default dtcg: dtcg (W3C design-token JSON) | css (custom properties on :root and .dark) | tailwind-v3 (config object) | tailwind-v4 (@theme block) | shadcn-registry (registry item) | json (the raw kit).
Behavior5/5

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

With no annotations, the description fully discloses behavior: 'Read-only: it returns the file contents as text and writes nothing to disk.' It also reveals the 403 error for entitled Pro kits, adding auth expectations beyond schema/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 three sentences, each earning its place: purpose, usage guidance, and behavioral transparency. It is front-loaded and free of filler.

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 read-only retrieval tool with 2 parameters and no output schema, the description covers all essential aspects: what it does, content scope, when to use, alternatives, side effects, and auth. It is sufficiently complete for an agent to select and invoke it correctly.

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 coverage is 100%, including detailed descriptions for both 'slug' and 'format' with enum values. The description adds only marginal context like 'format that matches the target stack,' but the schema already explains parameter semantics, so the baseline of 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 the tool fetches a design kit's machine-readable tokens in a format matching the target stack, specifying the content coverage (28 semantic color roles, typography, spacing). It distinguishes itself from siblings by explicitly contrasting with get_design_md and apply_theme.

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?

The description provides explicit guidance: 'Use it to wire a kit into an existing styling layer when you do not need the written brief; pair it with get_design_md when you also need the rules.' It also names apply_theme as the alternative for writing tokens into a project, covering when-not-to-use.

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/KasayoDotCom/identityforge-mcp'

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