Skip to main content
Glama

search_blocks

Find Bencho UI blocks (React components with their CSS and motion) by what they are or do — e.g. 'dropdown with bounce', 'confetti', 'drag to reorder'. Returns ids to pass to get_block.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return (default 10, max 30).
queryNoWhat you are looking for, in plain words.
categoryNoOptional: one of the categories from list_categories (Hover, Press, Drag, Slide, Swipe, Type, Select, Loading).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 behavioral burden. It discloses the key return behavior (ids) and the downstream get_block workflow, and 'Find' implies a read-only search, but it does not explain search ranking, matching semantics, or any operational constraints.

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 core action and resource. The examples and get_block linkage are compact and every sentence adds useful information without repetition.

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 simple three-parameter search tool with no annotations or output schema, the description covers purpose, example query style, and the return handoff to get_block. It does not describe ranking or result completeness, but the essential information needed to call it correctly is present.

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 already 100%, so the schema documents the parameters themselves. The description adds meaningful query semantics by showing that the query is natural-language description of a block's form or behavior, with examples like 'dropdown with bounce' and 'drag to reorder'.

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 and resource: find Bencho UI blocks, described as React components with CSS and motion. The examples ('dropdown with bounce', 'confetti', 'drag to reorder') make the resource concrete, and the note that results are ids for get_block clearly differentiates it from sibling retrieval tools.

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 makes clear that this is the discovery step before get_block, since it returns ids to pass to that tool. It also implies the query should describe what the block is or does, but it does not explicitly state when not to use it, such as when an id is already known.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources