Skip to main content
Glama

Get Tokens

get_tokens

Extract a Figma file's color and text styles as CSS custom properties for :root, so you can apply design tokens directly in web pages.

Instructions

The file's colour and text styles as CSS custom properties, for :root.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_url": "<file_url>"
    },
    "name": "get_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden and largely drops it. It reveals the output shape (CSS custom properties scoped to :root) but says nothing about whether this is a read-only fetch, whether it requires network access or auth, what happens on an invalid URL, or whether it caches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and the key information (CSS custom properties, :root) is front-loaded, but the sentence is a noun phrase with no verb, which reads as under-specification rather than tight writing.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but the description still leaves the input contract, read-only nature, and failure behavior unstated for a tool with a required parameter and zero annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter file_url, and the description never mentions it beyond the possessive 'The file's'. An agent gets no format hint (URL vs path vs ID) for the one input it must supply.

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

Purpose3/5

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

The fragment names the resource concretely ('colour and text styles as CSS custom properties, for :root'), so an agent can infer it extracts design tokens. But there is no verb and no statement that it *returns* anything, and it never distinguishes itself from siblings like get_layout or export_icons.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, no mention of when a caller should prefer this over get_layout or export_icons. The only implicit signal is that the output is CSS variables, which is a purpose statement, not usage guidance.

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