Search components by intent
search_componentsFind 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
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | 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. | |
| limit | No | Maximum results. | |
| query | Yes | What the UI should do, in plain words. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| results | Yes |