eds-mcp-server

by Edwson

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Get tokens

get_tokens

Return only the requested design token group and theme to avoid loading the entire system.

Instructions

Return only the requested token group (and theme for color). Avoids shipping the whole system.

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": {
      "group": "<group>"
    },
    "name": "get_tokens"
  }
}

Input Schema

Name	Required	Description	Default
`group`	Yes	color \| space \| radius \| type \| density
`theme`	No

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?

No annotations provided, so the description must cover behavior. It describes the return as a token group with optional theme for color. It does not mention side effects, errors, or permissions. Adequate for a simple read operation but could be more explicit.

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?

Single sentence, directly front-loaded with purpose. No fluff. Efficient and clear.

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 2-parameter tool without output schema or annotations, the description covers core functionality and usage context. Lacks details on response format or error cases, but adequate given simplicity.

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 description coverage is 50% (group has description, theme has enum only). The description mentions 'theme for color' adding context for the theme parameter, but does not elaborate on group values. Baseline 3 with modest additional value.

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 tool returns a specific token group and optionally a theme for color tokens. It distinguishes itself from siblings like list_token_groups by focusing on a single group.

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

Usage Guidelines4/5

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

The description implies use when needing a specific token group, mentioning efficiency ('avoids shipping the whole system'). It does not explicitly state when not to use or list alternatives, but the context is clear.

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