Skip to main content
Glama

Search labsUI

search
Read-only

Find labsUI components, blocks, hooks, helpers, and recipes by name, export, or intent; get matches with summaries and omitted counts.

Instructions

Find labsUI components, blocks, hooks and helpers by name, export (useModal) or intent (date range, toast promise), and recipes for a whole app (blog, shop): a prompt checked on a fresh app with the items it used. All words must match, best match first; no query lists everything. Returns one line per hit: name, kind and summary, and says how many a limit left out. Start here when you don't know an item's name, then call view on the hits.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOnly this kind: component (primitive), block (composed section), hook, helper, setup or recipe (a prompt for a whole app).
limitNoMost results to return. Default: 12 with a query, everything without one.
queryNoWords to match. Empty lists everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.9
    • changedInput schema / properties / kind / description
      Previous value: -"Only this kind: component (primitive), block (composed section), hook, helper or setup."New value: +"Only this kind: component (primitive), block (composed section), hook, helper, setup or recipe (a prompt for a whole app)."
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "component",
      -  "block",
      -  "hook",
      -  "helper",
      -  "setup"
      -]New value: +[
      +  "component",
      +  "block",
      +  "hook",
      +  "helper",
      +  "setup",
      +  "recipe"
      +]
  2. Changed2 schema fields changedv0.1.8
    • removedInput schema / properties / limit / default
      Removed value: -12
    • changedInput schema / properties / limit / description
      Previous value: -"Most results to return."New value: +"Most results to return. Default: 12 with a query, everything without one."
  3. Changed1 schema field changedv0.1.5
    • changedInput schema / properties / kind / description
      Previous value: -"Only items of this kind."New value: +"Only this kind: component (primitive), block (composed section), hook, helper or setup."
  4. Changed2 schema fields changedv0.1.4
    • addedInput schema / properties / kind / description
      Added value: +"Only items of this kind."
    • addedInput schema / properties / limit / description
      Added value: +"Most results to return."
  5. First observedv0.1.3

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: it discloses matching semantics (all words must match, best match first, empty query lists everything), result shape (one line per hit with name, kind, summary), truncation behavior (says how many a limit left out), and what a recipe is (a prompt checked on a fresh app). That is rich behavioral context an agent needs to interpret results correctly.

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?

Front-loaded with the core purpose and dense but purposeful throughout; every sentence adds matching rules, result format, or routing advice. It is somewhat run-on with parenthetical examples, but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the return-value burden and does so by describing one-line-per-hit format and omitted-count reporting. For a read-only search tool with fully covered parameters and clear routing guidance, nothing essential is 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 the schema already documents the three parameters. The description still adds meaning by explaining that the query can be a name, export, intent, or whole-app recipe, and by tying empty queries and limits to result behavior, which goes beyond the schema text.

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 ('Find') and resource (labsUI components, blocks, hooks, helpers, recipes) and specifies matching dimensions (name, export, intent). It distinguishes itself from siblings by naming the next step ('call view on the hits'), making it clearly a discovery tool rather than a detail, mutation, or diagnostics tool.

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?

Explicitly says 'Start here when you don't know an item's name, then call view on the hits,' which gives clear when-to-use guidance and names the follow-up alternative. It doesn't explicitly state when NOT to use it (e.g., when the name is already known), but the positive routing is strong.

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