Compose Preview Catalogs

ui_builder_search_components

Find catalog components by id, display name, Compose symbol, role or trait, e.g. TextField, text field, OutlinedTextField, Button, Card. Case, spaces, hyphens, underscores, slashes and camelCase are ignored, and the components the query names come first: an exact name, then a prefix, then a name containing it, then role and traits. Returns the same summary as ui_builder_list_catalogs (id, role, traits, slots, properties, and the catalog pin) for only the matches, so you don't pay for the whole catalog.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	Yes	Text to look for in a component's id, display name, Compose symbol, role or traits.
`token`	No	A grant token from poll_access, when you cannot set the X-Compose-Preview-Token header yourself — an MCP client fixes its headers at connect time, so this is how a token approved during this session is used in it. Prefer the header where you control it.
`catalog`	No	Only this catalog system id, e.g. m3-catalog. Omit to search every catalog; an id this server does not serve is an error.
`agentName`	No	Optional agent/client name shown to design viewers; self-reported.
`agentModel`	No	Optional current model name shown to design viewers; self-reported. Omit when unknown.
`catalogSystemId`	No	The same as `catalog`.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 12, 2026

changedInput schema / properties / catalog / description

Previous value: -"Only this catalog system id. Omit to search every catalog."New value: +"Only this catalog system id, e.g. m3-catalog. Omit to search every catalog; an id this server does not serve is an error."

addedInput schema / properties / catalogSystemId

Added value: +{
+  "description": "The same as `catalog`.",
+  "type": "string"
+}

changedInput schema / properties / query / description

Previous value: -"Text to look for in a component's id, role or traits."New value: +"Text to look for in a component's id, display name, Compose symbol, role or traits."

Changed2 schema fields changedOct 4, 2026

addedInput schema / properties / agentModel

Added value: +{
+  "description": "Optional current model name shown to design viewers; self-reported. Omit when unknown.",
+  "maxLength": 80,
+  "type": "string"
+}

addedInput schema / properties / agentName

Added value: +{
+  "description": "Optional agent/client name shown to design viewers; self-reported.",
+  "maxLength": 80,
+  "type": "string"
+}

Changed1 schema field changedSep 30, 2026
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "type": "object"
+}
```
First observedSep 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses normalization rules (case, spaces, hyphens, underscores, slashes, camelCase ignored) and an explicit ranking order (exact name, prefix, containing, then role/traits). It stops short of stating auth/permission scoping or whether results are paginated, so it is strong but not complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with the search scope before the ranking and return-payload details. Every clause adds information, though the second sentence is long and packs ranking and return-shape into one utterance.

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?

An output schema exists, so return values need not be spelled out, yet the description still characterizes the returned summary and its cost advantage. With 6 params fully documented in the schema and the token mechanics covered there, the description leaves little an agent needs missing.

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%, so baseline is 3, but the description adds real meaning to `query` by explaining matching fields, normalization, and result ordering beyond the schema's one-line description. It also implicitly clarifies the catalog-scoping behavior described in the schema for `catalog`/`catalogSystemId`.

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?

States a specific verb+resource ("Find catalog components") and enumerates exactly which fields are matched (id, display name, Compose symbol, role, trait), with concrete examples. It also explicitly contrasts itself with the sibling ui_builder_list_catalogs, so an agent can distinguish the two without opening schemas.

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?

It names the sibling ui_builder_list_catalogs and gives the selecting condition: search returns the same summary "for only the matches, so you don't pay for the whole catalog." That is clear context for when to prefer this tool, though there is no explicit when-not guidance beyond the cost tradeoff.

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

All Compose Preview Catalogs tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.