Skip to main content
Glama
Sign In
蓝湖 Design Schema MCP

蓝湖 Design Schema MCP

by andyjin5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lanhu_get_design_preview

Read-only

Retrieve a preview image of a design to verify overall visual appearance and check for text burned into layers.

Instructions

获取单张设计图的预览图片，用于确认整体视觉、图层是否烧录文字等。预览图不是几何权威来源；尺寸、坐标、颜色仍以 lanhu_get_design_schema 和 slices 为准。

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": {
      "url": "<url>"
    },
    "name": "lanhu_get_design_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes蓝湖 URL，pid 必需。支持 detailDetach（含 image_id）、stage/product 等格式，例：https://lanhuapp.com/web/#/item/project/detailDetach?tid=xxx&pid=xxx&image_id=xxx
designNo目标设计图：index 数字（lanhu_get_designs 返回的 index 字段）、设计图 id（uuid）或完整名称。URL 里已带 image_id 时可省略。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate read-only and open-world hints; description adds that preview is not authoritative for dimensions/colors, complementing annotations without contradiction.

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?

Two concise sentences, no filler, front-loaded with purpose and key limitation. Every sentence adds value.

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

Completeness5/5

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

Given simple tool with 2 params and no output schema, description sufficiently covers purpose, limitations, and sibling relationships; no gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters with descriptions; description adds context beyond schema, e.g., that 'design' can be omitted if image_id in URL, enhancing semantics.

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 the tool retrieves a preview image to confirm visuals and text burning, distinguishing it from schema and slices tools.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool (visual confirmation) and when not to (rely on schema/slices for authoritative geometry), providing clear guidance vs alternatives.

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

Deploy Server

Other Tools