Skip to main content
Glama
design-system-mcp
by dgesteves

Get design tokens

get_tokens
Read-onlyIdempotent

List design tokens with resolved values, dark-mode values and usage (Tailwind class or CSS variable). Filter by category or substring to get the right token instead of hardcoded hex codes or px values.

Instructions

List design tokens with resolved values, dark-mode values and how to use each (Tailwind class or CSS variable). Filter by category (color, spacing, radius, typography, shadow, other) or a substring. Use these instead of hex codes, px values or Tailwind default palette classes. Chart and sidebar colors are listed under their own headings: they are for charts and the sidebar, not for status colors.

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": "get_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoIn a monorepo served from its root: the file you are editing, or a project folder, relative to the root, to answer from that project. Without it, every project is listed together. Ignored in a single project. When the server was started outside your project, pass the file as an absolute path: the project is found from it.
queryNoSubstring to match in names, usages or descriptions.
categoryNoOnly tokens of this category.

Output Schema

NameRequiredDescriptionDefault
tokensYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.1
    • changedInput schema / properties / path / description
      Previous value: -"In a monorepo served from its root: the file you are editing, or a project folder, relative to the root, to answer from that project. Without it, every project is listed together. Ignored in a single project."New value: +"In a monorepo served from its root: the file you are editing, or a project folder, relative to the root, to answer from that project. Without it, every project is listed together. Ignored in a single project. When the server was started outside your project, pass the file as an absolute path: the project is found from it."
  2. First observedv0.6.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered; the description contributes by describing the shape of the content returned (resolved values, dark-mode variants, usage strings) and the result grouping for chart/sidebar tokens. Rate limits, pagination and project-scoping behavior are not mentioned, but the path parameter's schema text covers scoping.

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?

Three sentences, front-loaded with what the tool returns before the filtering and usage directives. Every sentence carries information; the chart/sidebar caveat is the only slightly tangential part, though it guards against a real misclassification.

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?

The tool is a read-only filtered list with a fully described three-parameter schema and an output schema, so return-value documentation is unnecessary. The description covers purpose, content, filtering, and the one behavioral trap (chart/sidebar vs status colors), leaving nothing an agent needs in order to call 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 description coverage is 100%, so all three parameters are already documented, including the path/monorepo behavior and the category enum. The description restates the category list and substring filtering rather than adding format examples, case sensitivity, or matching precedence. Baseline 3 is appropriate when the schema carries the semantics.

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 opens with a specific verb and resource ('List design tokens') and immediately enumerates what each entry contains: resolved values, dark-mode values, and usage form (Tailwind class or CSS variable). That distinguishes it cleanly from the component-oriented siblings (list_components, get_component, search_components), which do not deal in tokens at all.

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?

It gives a clear directive on when the output should be preferred: 'Use these instead of hex codes, px values or Tailwind default palette classes.' It also warns that chart and sidebar colors are listed under their own headings and are not for status colors, which prevents a plausible misuse. It stops short of naming an alternative tool or stating exclusions (e.g. when to use search_components instead), so it falls 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.