Skip to main content
Glama
Sign In
design-system-mcp

design-system-mcp

by erikadmoller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_components_by_category

List available design system components, optionally filtered by category, to find UI elements for your airline design.

Instructions

Lists all available components optionally filtered by category

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

Input Schema

NameRequiredDescriptionDefault
categoryNoCategory to filter by e.g. 'Fare display & selection'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 the full burden. It states 'Lists all available components' which implies a read-only operation, but does not explicitly confirm non-destructiveness, nor does it mention pagination, ordering, or return format. This is minimal behavioral disclosure.

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, front-loaded sentence with no filler. It earns a high score for brevity.

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?

Given the tool's simplicity (one optional parameter, no nested objects, no output schema), the description plus schema is sufficient for basic selection and invocation. However, the lack of any behavioral details (pagination, return shape) keeps it from being excellent, so a 4 is appropriate.

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?

The schema already documents the single optional 'category' parameter with 100% coverage. The description merely restates the filter concept without adding syntax, defaults, or format details, matching the baseline for high schema coverage.

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 clearly states the action ('Lists') and resource ('all available components') with an optional filter by category. It distinguishes from sibling tools by covering the list-all scenario, though it doesn't explicitly name alternatives.

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 indicates the tool can be used to list all components or filter by category, but provides no explicit guidance on when to choose this tool over get_component or find_component_for_use_case. The usage is implied rather than stated.

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