Search iDux UI components by keyword, optionally selecting Vue 2 or Vue 3, to retrieve relevant component documentation and usage examples.
通过关键词搜索idux组件（默认使用Vue3版本）
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | 搜索关键词 | |
| vueVersion | No | Vue版本（默认使用vue3） | vue3 |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are absent, so the description carries the full behavioral burden. It says nothing about result format, ranking, limits, or whether the search is fuzzy/exact. Only the default Vue version is hinted, but that's already in the schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single efficient sentence that front-loads the action. No waste, though it's too sparse to be truly helpful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a search tool with no annotations, no output schema, and siblings that overlap, the description should explain scope and relationship to list_idux_components but does not. It's incomplete for an agent to choose correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%; both query and vueVersion are documented in the schema. The description only restates the default version, which is redundant with the schema's default field. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a verb (search) and resource (idux components), which is clear. But it doesn't distinguish itself from sibling list_idux_components or get_component_details, leaving the boundary unclear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, no when-not-to-use, no mention of alternatives like list_idux_components. The Vue3 default is implied but not explained as an option.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.