Skip to main content
Glama

Search components

search_components
Read-only

Search four shadcn-format registries to find UI components, animated elements, hooks, and effects for insertion into code.

Instructions

Searches four shadcn-format registries: shadcn (base UI), reactbits (animated text, backgrounds, cursors), motion-primitives (animated components built with Motion) and fancy (effects and micro-interactions). Use get_component to see the code.

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": "search_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
queryNoE.g. dialog, text, cursor, marquee
registriesNoDefault: all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and external-search behavior. The description adds registry scope and the fact that code is retrieved via get_component, but it does not disclose result shape, pagination/limit behavior, or any auth/rate-limit details.

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?

Two sentences, front-loaded with the search scope and ending with the next-step pointer. The registry parentheticals are dense but each earns its place by clarifying what can be found.

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 simple search tool with four optional params, the description covers the registry dimension and the handoff to get_component, but it omits return-format/pagination information and most parameter meaning. With no output schema and only partial schema description coverage, an agent still has gaps to resolve.

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?

Schema coverage is 50%, and the description only explains the registries parameter by describing what each registry contains. It says nothing about type, query, or limit semantics, and the registry default ('all') is only in the schema, so it compensates only partially for the coverage gap.

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 description gives a specific verb ('Searches') and names four target registries with the content each covers: base UI, animated text/backgrounds/cursors, Motion components, and effects/micro-interactions. It also differentiates from get_component by directing code retrieval there, so an agent can identify the tool without opening the schema.

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?

It implies a search-then-fetch workflow by saying 'Use get_component to see the code,' which is useful next-step guidance. However, it does not explicitly state when to choose this search over other resource search tools or when not to use it, so usage is only implied.

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