Skip to main content
Glama
tokensqueezer-mcp

tokensqueezer-mcp

get_design_tokens

Extracts design tokens from the current Figma selection into W3C DTCG JSON for colors, multi-theme modes, typography, spacing, shadows, and gradients.

Instructions

Get design tokens from the current Figma selection in W3C Design Tokens Community Group (DTCG) JSON format, including colors, multi-theme modes, typography, spacing, shadows, and gradients.

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_design_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.7/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. "Get" implies read-only and the format plus token categories are disclosed, but it says nothing about behavior when nothing is selected, whether the selection walk is deep, size/rate limits, or failure modes — meaningful gaps for a selection-scoped extraction tool.

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?

A single front-loaded sentence with the source and format stated before the token enumeration. The list of token types (colors, multi-theme modes, typography, spacing, shadows, gradients) earns its place by helping an agent judge coverage for a request.

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

Completeness4/5

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

For a no-parameter tool with no output schema, the description supplies the essential return shape (DTCG JSON) and the categories returned. Only the selection prerequisite and empty-selection behavior are left unstated, which is a modest but real gap.

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 schema has zero parameters, so there is nothing for the description to clarify; baseline 4 applies. The description correctly implies the input is implicit (the current selection) rather than a passed argument.

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 and resource ("Get design tokens") plus the exact output format (W3C DTCG JSON) and the source scope (current Figma selection). It is distinguishable from siblings like get_design_spec by the explicit DTCG token framing, though it never names an alternative to contrast against.

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?

Usage is only implied: "from the current Figma selection" hints that a selection must exist and that tokens are wanted, but there is no explicit when-to-use, when-not, or pointer to get_design_spec for other needs. The agent must infer selection from the sibling set.

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