Skip to main content
Glama

start_ui

Automate UI development from a description. Checks design systems, generates component directories, and renders code for React, Vue, or HTML.

Instructions

统一 UI 开发编排工具 - 一键完成整个 UI 开发流程。自动检查设计系统、生成组件目录、搜索/生成模板、渲染最终代码。适合快速原型开发,保证整个项目样式统一。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYesUI 需求描述(如 '登录页面'、'用户列表'、'设置页面')
frameworkNo目标框架:react、vue、html(默认 react)react
templateNo模板名称(可选,不提供则自动生成)
template_profileNo模板档位:auto(默认,自动选择 guided/strict)、guided(普通模型友好)或 strict(结构更紧凑)auto
modeNo执行模式:auto(智能)/ manual(默认)manual
requirements_modeNo需求模式:steady(默认)或 loop(需求澄清与补全)
loop_max_roundsNo需求 loop 最大轮次(默认 2)
loop_question_budgetNo每轮最多提问数量(默认 5)
loop_assumption_capNo每轮假设上限(默认 3)
Behavior3/5

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

No annotations are provided, so the description carries full burden. It lists high-level steps (check design system, generate component directory, etc.) but does not disclose side effects, permissions, or whether files are modified. More detail on behavioral traits is needed.

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 two sentences, front-loaded with the core purpose, and contains no extraneous information. Every sentence adds value.

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?

The description explains the overall process and output (rendered code) but does not mention prerequisites (e.g., project initialization) or interaction with sibling tools. For a complex orchestrator with 9 parameters, it is mostly complete but could be slightly more detailed.

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 baseline is 3. The description does not add significant meaning beyond the schema's parameter descriptions; it focuses on the overall process rather than parameter details.

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 clearly states it is a unified UI development orchestration tool that automates the entire UI development process, from checking design systems to rendering code. It distinguishes itself from siblings like ui_design_system and ui_search by positioning as a one-click complete solution for rapid prototyping.

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 description identifies usage context (适合快速原型开发) but does not provide explicit when-not-to-use or alternatives. It implies suitability for rapid prototyping but lacks exclusions or comparisons to sibling tools.

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