Skip to main content
Glama

Tseha

by io.tseha

Get design tokens

get_style_tokens
Read-only

Returns the project's design tokens with their names, values, and token paths. Read-only. Use it to source exact visual values for styling instead of inventing hex codes, spacing, or radii. The category argument takes exactly one of: color, typography, spacing, radius, shadow, blur, all; omitting it behaves the same as "all". Pass a single category when you know which one you need - "all" returns the largest response this server produces. Use get_style first if you only need to know which categories exist, and get_standards for coding conventions, which are not tokens. A project with no style configured returns an empty token list with a note, not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoOne of: color, typography, spacing, radius, shadow, blur, all
project_idYesUUID as returned by list_projects - not the project name, title, or slug, and not guessable. Fetch it once and reuse the same id across tools. An id outside the caller's organization returns "Project not found or access denied" rather than empty data, and a project withheld by a plan limit returns a plan error that retrying cannot clear. Tokens come from the style assigned to this project. A style is assigned per project with no organization-level fallback, so a project with no style assigned returns an empty token list, not the tokens of a sibling project.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / project_id / description
      Previous value: -"UUID as returned by list_projects - not the project name, title, or slug, and not guessable. Fetch it once and reuse the same id across tools. An id outside the caller's organization returns \"Project not found or access denied\" rather than empty data, and a project withheld by a plan limit returns a plan error that retrying cannot clear. Tokens come from the style this project resolves to, which may be a project-level override rather than the organization default."New value: +"UUID as returned by list_projects - not the project name, title, or slug, and not guessable. Fetch it once and reuse the same id across tools. An id outside the caller's organization returns \"Project not found or access denied\" rather than empty data, and a project withheld by a plan limit returns a plan error that retrying cannot clear. Tokens come from the style assigned to this project. A style is assigned per project with no organization-level fallback, so a project with no style assigned returns an empty token list, not the tokens of a sibling project."
  2. Changed1 schema field changed
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID from list_projects"New value: +"UUID as returned by list_projects - not the project name, title, or slug, and not guessable. Fetch it once and reuse the same id across tools. An id outside the caller's organization returns \"Project not found or access denied\" rather than empty data, and a project withheld by a plan limit returns a plan error that retrying cannot clear. Tokens come from the style this project resolves to, which may be a project-level override rather than the organization default."
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond the read-only hint, the description discloses non-obvious behavior: omitting category is equivalent to 'all', 'all' returns the largest response this server produces, and an unconfigured project returns an empty token list with a note rather than an error. It also details plan/access error behavior for project_id, which is exactly the kind of context a caller needs.

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 a compact but information-dense paragraph. Each sentence earns its place: the first states the core return value, the second reinforces the read-only nature and primary intent, the third clarifies argument semantics, and the final covers alternatives and error behavior. No filler words, no repetition.

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?

With two params and no output schema, the description covers everything a caller could need: what tokens are, how category behaves, what the largest response is, how a missing style manifests, and how project_id errors appear. The inclusion of empty-list behavior and access-denied error messaging is thorough for a read-only tool.

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

Parameters5/5

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

Even though schema coverage is 100%, the description adds meaning that the schema alone does not: the category omission behavior ('behaves the same as all') and the project_id guidance ('not the project name, title, or slug... Fetch it once and reuse the same id', plus access/plan error scenarios). This significantly enriches what an agent knows before calling.

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 verb 'Returns' and the resource 'design tokens with their names, values, and token paths.' It stands out from siblings by explaining that get_style is for category discovery and get_standards is for coding conventions, so an agent can immediately tell this tool APIs apart without opening schemas.

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?

It explicitly explains when to use it ('source exact visual values for styling instead of inventing hex codes, spacing, or radii'), when to use a single category, and names alternatives: 'Use get_style first if you only need to know which categories exist, and get_standards for coding conventions, which are not tokens.' A clear set of conditions.

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

All Tseha toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.8/5.0
Disambiguation5/5

Each tool has a clearly distinct resource and role: enumeration (list_*), lookup (get_*), search, updates, and metadata. Even the closely related list_components and search_components are sharply separated by exact-name enumeration versus ranked by-use-case search.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern, using either list_* for enumerations or get_* for single-item or metadata lookups. Naming choices clearly signal the operation type and resource without exceptions.

Tool Count5/5

With 9 tools, the server is well-scoped for read-only access to a project's design system, component catalog, standards, and style tokens. Each tool has a distinct responsibility and none feel redundant or superfluous.

Completeness5/5

The surface fully covers the read-only domain: project discovery, package listing, component enumeration and search, component details, version updates, standards, and style tokens. It leaves no obvious dead ends for an agent needing design system information.

Resources