eds-mcp-server

Overview Schema Source Related Servers Discussions Admin

List consumer components

list_consumer_components

Retrieve consumer design system components, optionally filtered by domain (e.g., ai, commerce, growth). Returns id, name, domain, platform anchor, and canonical URL.

Instructions

The Consumer Design System (B2C sibling, 118 categories / 11 domains incl. a 22-entry AI & Agents domain). List entries — id, name, domain, platform anchor, canonical URL — optionally filtered by domain (e.g. "ai", "commerce", "growth").

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": "list_consumer_components"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	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. The description indicates a read operation (listing), which is safe, but does not disclose additional behavioral traits such as pagination, authentication, or rate limits.

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 two sentences, front-loading important system context (118 categories, 11 domains) followed by the tool's function, with no unnecessary words.

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 list tool with one optional parameter and no output schema, the description covers returned fields and filter capability. It lacks pagination details but is otherwise adequate given the tool's simplicity.

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?

With 0% schema description coverage, the description adds value by explaining the domain parameter is optional and giving concrete examples (e.g., 'ai', 'commerce', 'growth'), partially compensating for the schema gap.

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 specifies the tool lists entries from the Consumer Design System (B2C sibling), enumerates returned fields (id, name, domain, platform anchor, canonical URL), and mentions optional domain filtering, distinguishing it from siblings like list_components.

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 it's for B2C components and provides domain filter examples, but does not explicitly state when to use this tool over alternatives like search_consumer_components or list_components, nor does it mention exclusions.

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