Skip to main content
Glama
mybolide

MCP Probe Kit

by mybolide
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

ui_search

Read-onlyIdempotent

Search UI pages, components, and interaction specs by task or keyword. Use structure mode for task-based info architecture, or search, catalog, and template modes for broader discovery.

Instructions

搜索页面结构、组件、交互规范和实现参考。新 UI 流程优先使用 structure 模式按任务和页面类型选择信息架构；旧 search/catalog/template 模式继续兼容。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNostructure（页面结构，推荐）、search（通用数据）、catalog（组件目录）、template（旧模板兼容）。search
limitNo返回结果数量。structure 模式默认 3、最多 5；其他模式默认 10、最多 50。
queryNo核心任务或搜索关键词。structure 模式应描述用户要完成的任务。
stackNosearch 模式技术栈过滤。
densityNostructure 模式的目标内容密度。
categoryNosearch 模式数据类别：colors、icons、charts、landing、products、typography、styles、ux-guidelines、shadcn-blocks、shadcn-components、ui-themes、ui-guidelines-vercel。
min_scoreNosearch 模式最小相关性得分。
screen_typeNostructure 模式的页面类型，如 professional-dashboard、workflow-console、marketing-page、commerce-catalog。

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed9 schema fields changedv4.0.0
    • changedInput schema / properties / category / description
      Previous value: -"数据类别（search 模式）：colors、icons、charts、landing、products、typography、styles、ux-guidelines、shadcn-blocks、shadcn-components、ui-themes、ui-guidelines-vercel 等"New value: +"search 模式数据类别：colors、icons、charts、landing、products、typography、styles、ux-guidelines、shadcn-blocks、shadcn-components、ui-themes、ui-guidelines-vercel。"
    • addedInput schema / properties / density
      Added value: +{
+  "description": "structure 模式的目标内容密度。",
+  "enum": [
+    "compact",
+    "comfortable",
+    "spacious"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"返回结果数量（默认 10，范围 1-50）"New value: +"返回结果数量。structure 模式默认 3、最多 5；其他模式默认 10、最多 50。"
    • changedInput schema / properties / min_score / description
      Previous value: -"最小相关性得分（默认 0，范围 0-100）"New value: +"search 模式最小相关性得分。"
    • changedInput schema / properties / mode / description
      Previous value: -"搜索模式：search（搜索 UI/UX 数据，默认）、catalog（查看组件目录）、template（搜索 UI 模板）"New value: +"structure（页面结构，推荐）、search（通用数据）、catalog（组件目录）、template（旧模板兼容）。"
    • addedInput schema / properties / mode / enum
      Added value: +[
+  "structure",
+  "search",
+  "catalog",
+  "template"
+]
    • changedInput schema / properties / query / description
      Previous value: -"搜索关键词（支持中英文，如 'button'、'按钮'、'primary color'、'主色调'）。catalog 模式不需要此参数。"New value: +"核心任务或搜索关键词。structure 模式应描述用户要完成的任务。"
    • addedInput schema / properties / screen_type
      Added value: +{
+  "description": "structure 模式的页面类型，如 professional-dashboard、workflow-console、marketing-page、commerce-catalog。",
+  "type": "string"
+}
    • changedInput schema / properties / stack / description
      Previous value: -"技术栈过滤（仅 search 模式）：react、vue、nextjs、nuxtjs、svelte、astro、flutter、react-native、swiftui、jetpack-compose 等"New value: +"search 模式技术栈过滤。"
  2. Changed1 schema field changedv3.6.3
    • changedInput schema / properties / category / description
      Previous value: -"数据类别（仅 search 模式）：colors（颜色）、icons（图标）、charts（图表）、landing（落地页）、products（产品）、typography（字体）、styles（样式）、ux-guidelines（UX 指南）、web-interface（Web 界面）等"New value: +"数据类别（search 模式）：colors、icons、charts、landing、products、typography、styles、ux-guidelines、shadcn-blocks、shadcn-components、ui-themes、ui-guidelines-vercel 等"
  3. Addedv3.0.16

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, covering the safety profile. The description adds context about mode behavior (e.g., structure mode limits) but does not disclose additional behavioral traits such as authorization requirements or rate limits. No contradiction with annotations.

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?

The description is extremely concise: two sentences that front-load the core purpose and immediately follow with mode guidance. Every sentence serves a clear purpose without repetition or fluff.

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?

Given 8 optional parameters, no output schema, and annotations present, the description covers the modes and usage well. It could be more complete by describing the return format or result structure, but the mode descriptions and parameter schema together provide sufficient context for an agent to use the tool correctly.

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 parameters are well-documented in the schema. The overall description does not add significant meaning beyond what each parameter's description already provides. Baseline score of 3 is appropriate as the schema carries the burden.

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?

The description clearly states the tool searches for page structures, components, interaction specs, and implementation references. It distinguishes between four modes (structure, search, catalog, template) and recommends structure mode for new UI processes. However, it does not explicitly differentiate this tool from sibling tools like ui_design_system.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides internal mode usage guidance: prefer structure mode for new UI processes, while old modes remain compatible. It does not, however, give guidance on when to use this tool versus alternative sibling tools, nor does it mention excluded scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mybolide/mcp-probe-kit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server