EneUI Catalogue

search_blocks

Search composed UI blocks (hero, pricing, navbar, blog, dashboard…). A block is a whole section published by its author as registry:block, not a single component. Returns the block page, its dependencies and the source registry.

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

Input Schema

Name	Required	Description
`limit`	No	How many results (default 10).
`query`	Yes	What the section must do: 'pricing three tiers', 'hero with video', 'footer with newsletter'.
`source`	No	Optional registry id (e.g. shadcn, shadcn-ui-blocks).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose the return payload ('the block page, its dependencies and the source registry') plus the registry:block typing that governs results. It leaves out ordering/relevance behavior and any pagination or error semantics beyond the limit parameter, which keeps it from a 5.

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?

Three short sentences, front-loaded with the core purpose, followed by the definitional disambiguation and the return summary. Every sentence contributes distinct information with no filler.

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?

With no output schema, the description supplies a brief return summary and the essential block-vs-component framing for a three-parameter search tool. It is complete enough to call correctly, with only minor gaps around result ordering and how dependencies are represented.

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 description coverage is 100%, so all three parameters are already documented in the schema, including the query examples and the source registry id. The description adds no parameter-level detail beyond that, so the baseline of 3 applies.

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 ('Search') and resource ('composed UI blocks') with concrete examples (hero, pricing, navbar, blog, dashboard) and explicitly defines the unit as a 'whole section published ... as `registry:block`, not a single component'. That negative definition lets an agent distinguish it from search_components without opening either schema.

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?

Usage context is clear: this tool is for whole sections, and the 'not a single component' clause implicitly routes single-component lookups to search_components. It stops short of naming that sibling or giving explicit when-not conditions (e.g. when to use get_block after finding a block), so it falls just short of a 5.

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

All EneUI Catalogue tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?