Skip to main content
Glama
design-system-mcp
by dgesteves

Search components by intent

search_components
Read-onlyIdempotent

Find a React design-system component by describing the UI behavior you need; ranks matching names, props, variants, and docs, and marks weak results when no component clearly fits.

Instructions

Find components by what you want to build, e.g. "confirm a destructive action", "status label", "text field with validation". Ranks names, descriptions, docs, props and variant values with BM25 (local, no API key). When no component clearly matches, it says so and lists the nearest, marked weak. Use it when you do not know which component fits.

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": {
      "query": "<query>"
    },
    "name": "search_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoIn a monorepo served from its root: the file you are editing, or a project folder, relative to the root, to answer from that project. Without it, every project is listed together. Ignored in a single project. When the server was started outside your project, pass the file as an absolute path: the project is found from it.
limitNoMaximum results.
queryYesWhat the UI should do, in plain words.

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.1
    • changedInput schema / properties / path / description
      Previous value: -"In a monorepo served from its root: the file you are editing, or a project folder, relative to the root, to answer from that project. Without it, every project is listed together. Ignored in a single project."New value: +"In a monorepo served from its root: the file you are editing, or a project folder, relative to the root, to answer from that project. Without it, every project is listed together. Ignored in a single project. When the server was started outside your project, pass the file as an absolute path: the project is found from it."
    • addedOutput schema / properties / results / items / properties / weak
      Added value: +{
      +  "description": "Set when no component clearly matches the query: each result has only a word or two in common with it.",
      +  "type": "boolean"
      +}
  2. First observedv0.6.0

TDQS

A4.9/5.0
Behavior5/5

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

The description adds critical behavioral details beyond annotations, such as the search mechanism (BM25), the breadth of the search (names, docs, props, and variants), and the handling of weak matches.

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 dense but extremely efficient, front-loading the core functionality and quickly detailing its scope and logic in under 60 words.

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

Completeness5/5

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

Given the complexity of querying a component library, the description is highly complete. It explains the search scope, the ranking mechanism, and the uncertainty handling, which are all essential for successful tool use.

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?

Although the schema coverage is 100%, the description adds vital semantic context to the 'path' parameter (monorepo structure, relative vs. absolute paths). It also provides excellent examples of the required 'query' 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 tool clearly identifies its purpose as finding components based on intent, distinct from list_components or get_component. The title and description frame it as a search mechanism for architectural discovery.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use the tool: 'Use it when you do not know which component fits.' This clarifies its role in the component discovery workflow.

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