BrixUI MCP Server

search_brix_components

Find BrixUI components by name, category, or description using fuzzy matching and optional category filters.

Instructions

Search BrixUI components by name, category, or description. Supports fuzzy matching and optional category 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": {
      "query": "<query>"
    },
    "name": "search_brix_components"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	Search term (e.g. 'button', 'card', 'input')
`category`	No	Optional category filter (e.g. 'Buttons', 'Cards', 'Navigation')
`limit`	No	Maximum results to return (default: 20)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jun 24, 2026

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 full burden. It mentions fuzzy matching and optional category filtering, but fails to disclose what the tool returns (e.g., full component objects or just IDs), pagination behavior beyond the limit parameter, or any side effects.

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 sentence with no redundant words. It is front-loaded with the core function and efficiently conveys key features.

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?

For a search tool with 3 parameters and no output schema, the description is adequate but incomplete. It does not describe the return format (e.g., list of component names or details) or mention pagination limits beyond the parameter definition. The context from siblings helps but is not explicit.

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?

Schema coverage is 100% with parameter descriptions. The tool description adds value by specifying 'fuzzy matching' for the query parameter and 'optional category filtering' for the category parameter, which enhances understanding beyond the schema alone.

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 'Search BrixUI components by name, category, or description', which defines a specific verb and resource. It implies distinction from siblings like 'list_brix_components' but does not explicitly differentiate when to use search vs list.

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 usage for searching with fuzzy matching and filtering, but lacks explicit guidance on when to use this tool versus alternatives like 'list_brix_components'. No 'when not to use' or prerequisites are mentioned.

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

Deploy Server