Skip to main content
Glama

UI 截图转代码/规格

ui_to_artifact

Convert UI screenshots or design images into runnable code or structured specifications. Supports defining target framework, detail level, and region of interest for tailored frontend output.

Instructions

把一张 UI 截图/设计稿转成可运行代码或结构化规格。当宿主拿到界面图、需要据此生成或还原前端实现时使用。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYes图片:本地路径 / file:// / http(s):// / data: URI
targetNo产出 code(默认)或 spec
frameworkNo目标框架,如 react/vue/html
questionNo具体问题或额外要求
detail_levelNo细节级别:overview=单次快速;normal/fine/auto 触发由粗到细的自动缩放(auto 为默认,足够清晰则早退)
regionNo可选:手动指定关注区域,命名如 'top-right' 或归一化 bbox 'x,y,w,h'(0~1)
thinkingNo是否开启视觉模型深度推理(默认按工具/后端策略)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
markdownYes人类可读的结构化 markdown 正文(与 content 一致)
confidenceNo模型对结果的置信度
roundsYes实际经历的视觉调用轮数
regionsNo缩放走过的区域轨迹(归一化 bbox)
warningsYes降级/截断/不确定等告警
providerYes
modelYes
Behavior1/5

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

No annotations are provided, so the description must cover behavioral traits. It fails to disclose any side effects, latency, or model dependencies, leaving the agent unaware of potential issues.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short (two sentences) and front-loaded, which is positive. However, it omits critical details that could be included concisely, balancing brevity with completeness poorly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (7 parameters, output schema), the description is incomplete. It does not explain how parameters like detail_level or region affect behavior, nor the output schema structure, leaving gaps for the agent.

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 baseline is 3. The description adds no additional meaning beyond the schema; it merely restates the conversion purpose without parameter-specific insights.

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 converts UI screenshots to code or structured specifications and provides a usage context. However, it does not differentiate from sibling tools like image_analysis, which could confuse the agent.

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 implies when to use (when having a UI screenshot needing frontend implementation) but lacks explicit exclusions or alternatives. It does not mention when not to use, which is a gap.

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/Pelican0126/vision-mcp'

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