Skip to main content
Glama

Tseha

by io.tseha

Get style metadata

get_style
Read-only

Returns metadata for the project's active style: the style name, its Figma file key, when it was last synced, and a token count per available category (such as color, typography, spacing). Read-only and small - it names categories but returns no token values. Use it to inspect the project theme, or to learn which categories are populated before requesting values; call get_style_tokens for the values themselves. project_id is the only argument and it is not a plain filter: a style is assigned per project and there is no organization-level fallback, so sibling projects can report different style names and different populated categories, and a project with no style assigned returns a null style with a note rather than an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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. A style is assigned per project and there is no organization-level fallback, so sibling projects can report different styles and different populated categories, and a project with no style assigned returns a null style.

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. The active style is resolved per project: a project-level override beats the organization default, so sibling projects can report different styles and different populated categories."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. A style is assigned per project and there is no organization-level fallback, so sibling projects can report different styles and different populated categories, and a project with no style assigned returns a null style."
  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. The active style is resolved per project: a project-level override beats the organization default, so sibling projects can report different styles and different populated categories."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint=true annotation, the description discloses that the tool returns no token values, that style assignment is project-scoped with no organization-level fallback, and that a project with no style returns a null style with a note rather than an error. This is meaningful behavioral context that the annotation does not provide.

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?

The description is front-loaded and the core return semantics are stated immediately. The final sentence is useful but dense, mixing scoping rules with edge-case behavior; it is still economical and every sentence earns its place.

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 tool with one parameter, no output schema, and a safe annotation, this description is complete: it names the return fields, clarifies the absence of token values, names the recommended next tool, and covers the most relevant edge case. Nothing needed to call it correctly is left out.

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 input schema already describes project_id at 100% coverage, so the baseline is 3. The description adds useful semantics by explaining that project_id is not a plain filter: styles are per-project, sibling projects can differ, and an unassigned style produces a null-style result. That extra meaning justifies moving above baseline without over-explain

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: 'Returns metadata for the project's active style,' then lists exactly what is returned: name, Figma file key, last synced time, and token count per category. It also names the sibling get_style_tokens, so the agent can distinguish this tool without reading other definitions.

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 says 'Use it to inspect the project theme, or to learn which categories are populated before requesting values; call get_style_tokens for the values themselves.' This gives explicit usage context and names the alternative, so the agent knows when this tool is preferred.

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