Skip to main content
Glama
Sign In
lanhu-mcp-server

lanhu-mcp-server

by DC911360
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

lanhu_download_design

Download design drafts from Lanhu by extracting HTML/CSS code and images, replacing CDN URLs with local paths for offline use.

Instructions

一键下载蓝湖设计稿：通过 Puppeteer 从 DDS 页面提取官方生成的 HTML/CSS 代码 + 下载所有 CDN 切图并替换为本地路径。输出 index.html / index.css / flexible.js / common.css + img/。

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": {
      "imageId": "<imageId>",
      "outputPath": "<outputPath>"
    },
    "name": "lanhu_download_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageIdYes设计稿 image_id（从蓝湖 URL 中获取）
projectIdNo项目 UUID（不传则使用默认配置）
outputPathYes输出目录路径（如 ~/Desktop/my-design）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A4/5.0
Behavior4/5

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

The description discloses the process: Puppeteer extraction, CDN download, and local path replacement. It clearly indicates the output files and that the tool modifies local disk. This is detailed despite no annotations.

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

Conciseness4/5

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

The description is a single sentence that packs significant detail, but it is somewhat dense and could be broken into shorter sentences for easier parsing. Front-loading with the main action is good.

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?

The description explains the full output (index.html, index.css, etc.) and the process, compensating for the lack of an output schema. It covers all necessary context for a download tool.

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 the schema already describes parameters. The description adds context for imageId and outputPath (e.g., 'from URL', 'output directory') but does not elaborate on projectId. This provides marginal value over the schema.

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's purpose: downloading Lanhu design drafts, extracting HTML/CSS via Puppeteer, downloading CDN images, and replacing paths. It lists output files, distinguishing it from sibling tools like lanhu_download_cover or lanhu_download_image.

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 usage for downloading a full design draft, but lacks explicit guidance on when to use this tool versus alternatives (e.g., lanhu_download_cover for covers only). No when-not-to-use or prerequisite information is provided.

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