Skip to main content
Glama

Search Klarhimmel UI

search_items
Read-only

Read-only and free. Search the Klarhimmel UI catalogue (blocks, components, app screens, templates) by words in name, title or description. Returns up to 20 matches with name, kind, title and description; pass a name to get_item for the install command.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOnly this kind of item.
queryYesWords to look for, e.g. "pricing" or "hero with image".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds genuinely new context: a result cap of 20 and the exact fields returned (name, kind, title, description). "Free" is a cost note not captured in annotations, which is useful. It does not describe ranking/relevance behavior or what happens when no match is found, keeping it below 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?

Two sentences, zero waste, and the most important qualifier (read-only, free) plus the routing advice are front-loaded. Every clause carries information the agent needs.

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?

There is no output schema, and the description compensates by stating the return shape and the 20-result cap. Combined with the sibling handoff to get_item, an agent has everything needed to call this correctly and act on the results.

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 the schema already documents both parameters including the enum values, making 3 the baseline. The description adds some value by mapping `query` to the specific searchable fields (name, title or description), but it adds nothing about the `kind` filter beyond what the enum provides.

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 names a specific verb and resource ("Search the Klarhimmel UI catalogue") and enumerates the item kinds it covers (blocks, components, app screens, templates). It also states which fields are matched (name, title, description), so the agent knows exactly what class of operation this is and can tell it apart from get_item.

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 workflow handoff is explicit: "pass a name to get_item for the install command," which tells the agent when to leave this tool for a sibling. It lacks an explicit "don't use this when..." exclusion (e.g., when you already know the exact item), 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources