Skip to main content
Glama
Sign In
Design System MCP Server

Design System MCP Server

by appian-design
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search-design-system

Search components, layouts, and patterns by keyword. Filter by source (public, internal, or all) and optionally include internal documentation.

Instructions

Search for components, layouts, or patterns by keyword with source filtering

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": {
      "keyword": "<keyword>"
    },
    "name": "search-design-system"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesKeyword to search for in titles and descriptions
includeInternalNoInclude internal documentation in search (default: false)
sourceOnlyNoFilter results by specific source

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It fails to disclose any behavioral traits such as pagination, rate limits, authentication requirements, or what happens with no results. Only states the basic search function.

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?

A single concise sentence that conveys the core functionality without any filler. Every word is meaningful and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description should hint at return values or structure. It does not. For a search tool with 3 parameters and one enum, additional context like search result format would improve completeness. Score reflects minimum viability.

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 100%, so the schema already documents all parameters well. The description adds only a summary ('by keyword with source filtering') without enriching meaning beyond the schema. Baseline 3 is appropriate.

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 searches for components, layouts, or patterns by keyword with source filtering. It uses a specific verb and resource, and distinguishes itself from sibling tools like list-components (lists all) and get-component-details (specific item).

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 you need to find design system items by keyword and filter by source. However, it does not explicitly state when not to use it (e.g., when you already know the component name or want all items). Siblings provide context but are not mentioned.

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

Deploy Server

Other Tools