Skip to main content
Glama
Sign In
uikit-registry

uikit-registry

by captainy7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_component

Search for a UI component across 13 popular libraries to find which libraries include it. Filter results by library name if needed.

Instructions

Cari komponen UI di semua library. Return daftar library yg punya komponen itu.

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_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNama komponen yg dicari (contoh: button, dialog, pagination, card, modal, table, form, input, select, navbar, sidebar, dll)
libraryNoFilter hasil hanya dari library tertentu (contoh: shadcn, mui)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the return is a list of libraries, but doesn't specify search behavior like case sensitivity, partial matching, or result limits. Adequate but not detailed.

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 extremely concise: two sentences clearly stating purpose and return value. No unnecessary information.

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?

For a search tool with 2 parameters and no output schema, the description is largely complete. It explains what it does and what it returns, though it lacks notes on empty results or errors.

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 good descriptions for both parameters (query with examples, library filter). The tool description adds that the result is a list of libraries, complementing the schema well.

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 uses a specific verb ('Cari' meaning search) and resource ('komponen UI'), and clearly distinguishes from siblings (compare_components, get_component) by stating it searches across all libraries and returns a list of libraries.

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?

The description clearly states when to use this tool (to find which libraries have a UI component), but lacks explicit exclusions or alternatives. However, the sibling tools provide context for differentiation.

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

Deploy Server

Other Tools