Skip to main content
Glama

Search UI patterns by description

search_ui_patterns
Read-onlyIdempotent

Finds the conventional name of a UI element or design pattern from a plain-language description, question or term — e.g. "the bar at the bottom of an app", "three horizontal lines icon", "the black bar at the top of iPhone", "汉堡菜单". Searches CatchUI's curated catalog of 98 patterns and returns names in English and Chinese, definitions, the best-matching Q&A and each entry's catalog URL. Use when someone asks what a UI element is called or what a UI/UX term means.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of matches to return.
queryYesDescription, question, or name of a UI element, in English or Chinese.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's value lies in what else it discloses: the catalog size (98 patterns), the language coverage (English and Chinese), and exactly what each result contains (names, definitions, best-matching Q&A, catalog URL). Given there is no output schema, this return-shape detail is genuinely useful; it stops short of describing empty-result or limit behavior.

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?

Two sentences, front-loaded with the capability and followed by the trigger condition. Four inline examples are slightly more than strictly needed, but each illustrates a distinct input style (spatial description, icon shape, device-specific term, Chinese term) so none is pure 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?

For a simple two-parameter read-only search with no output schema, the description supplies the essentials: what it matches on, what comes back, catalog scope, and language support. Missing only minor operational details such as what happens when nothing matches and how `limit` affects the response.

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 coverage is 100%, so both parameters are already documented, placing this at the baseline. The description does add usable nuance to `query` by showing that natural-language questions, colloquial spatial descriptions ("the bar at the bottom of an app"), and non-English terms all work, but it says nothing about `limit` or result-count behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Finds") and resource ("the conventional name of a UI element or design pattern") and reinforces it with four concrete example queries. It does not explicitly distinguish itself from siblings such as get_ui_component_names or get_ui_pattern, which is the only thing keeping it from a 5.

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?

"Use when someone asks what a UI element is called or what a UI/UX term means" gives a clear trigger condition for invocation. There is no when-not-to-use guidance and no routing to the other five sibling tools, so the agent must infer alternatives.

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