eds-mcp-server

Overview Schema Source Related Servers Discussions Admin

Export theme

export_theme

Export the complete design token set as CSS, JSON, SCSS, or Tailwind config. Supports dual themes and maintains consistency with component variable names.

Instructions

Emit the whole token set as ready-to-use css | json | scss | tailwind. Dual-theme, self-consistent with scaffold_component variable names.

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": {
      "format": "<format>"
    },
    "name": "export_theme"
  }
}

Input Schema

Name	Required	Description	Default
`format`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.17.0Jul 29, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It mentions the output is 'dual-theme' and 'self-consistent with scaffold_component variable names,' which adds useful context. However, it does not mention whether the operation is read-only, any auth requirements, or what happens on failure. The description partially reveals the tool's nature but lacks completeness.

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 single sentence that front-loads the action and resource, then efficiently adds key context about themes and consistency. Every word adds value, with no redundancy or filler.

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 simple export tool with one parameter and no output schema, the description covers the purpose, formats, and thematic consistency. However, it does not specify the exact return type (e.g., string, file) or behavior in edge cases, which an agent might need. The absence of output schema increases the need for such details, but the description is nearly complete.

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 has a single required parameter 'format' with an enum, but its description coverage is 0%. The description compensates by listing the formats ('css | json | scss | tailwind') and adding meaning with 'ready-to-use' and 'dual-theme, self-consistent.' This provides context beyond the raw enum values, though it could clarify the specific output for each format.

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 action ('Emit'), the resource ('the whole token set'), and the target formats ('css | json | scss | tailwind'). It also mentions dual-theme and consistency with scaffold_component, which distinguishes it from sibling tools like get_tokens or list_token_groups that focus on inspection rather than export.

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?

The description implies when to use the tool (to export the entire token set in a specified format), but it does not explicitly state when not to use it or suggest alternatives. Sibling tools like get_token or list_token_groups provide context for alternative use cases, but no direct guidance is given.

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