Skip to main content
Glama
MCP Design System Extractor

MCP Design System Extractor

get_theme_info

Extract design system theme details—colors, spacing, typography, and breakpoints—to guide styling decisions and refactoring.

Instructions

Get design system theme information (colors, spacing, typography, breakpoints)

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

Input Schema

NameRequiredDescriptionDefault
includeAllNoWhether to include all CSS custom properties found (default: false)

Output Schema

NameRequiredDescriptionDefault
themeYes
totalTokensYes
sourceStoryIdYesThe story the tokens were read from

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0
  2. Removedv1.2.0
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; 'Get' does communicate a read-only, non-destructive operation. However, it says nothing about cost or payload behavior when includeAll is enabled, or whether the result reflects a default versus a configured theme. For a lightweight getter this is acceptable but not rich.

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?

One front-loaded sentence with a parenthetical enumeration of returned data categories; no filler or redundancy. It could be marginally tighter but every element contributes.

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?

The tool is simple, has one optional parameter with full schema documentation, and an output schema that covers return values, so the description need not describe the response shape. The only residual gap is the absence of any note about the includeAll flag's impact, which is minor here.

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 coverage is 100% and the single optional parameter includeAll is documented in the schema with its default, so the description is not required to explain it. The description adds no meaning about what 'all CSS custom properties' implies for response size, so baseline 3 applies.

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?

The description gives a specific verb and resource ('Get design system theme information') and enumerates the returned categories (colors, spacing, typography, breakpoints), which clearly separates it from component-oriented siblings like list_components or get_component_html. It stops short of naming an adjacent alternative such as get_external_css, so it is not a full 5.

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?

There is no guidance on when to call this tool, when to prefer a sibling, or what prerequisite conditions apply (e.g. whether a configured theme is required). The only usage signal is implicit in the word 'Get'.

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