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

lanhu-mcp-server

by DC911360
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

lanhu_generate_code

Generate frontend code (Vue 3 or HTML) from Lanhu DDS semantic design data by specifying an image ID.

Instructions

基于蓝湖 DDS 语义化数据生成前端代码。支持 Vue 3 SFC (.vue) 和 HTML 输出。

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>"
    },
    "name": "lanhu_generate_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNo输出格式：vue 或 htmlvue
imageIdYes设计稿 image_id
outputPathNo输出目录（不传则返回代码内容）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided; description only mentions code generation and output formats. Does not disclose side effects, permissions, idempotency, or error behavior.

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?

Two concise sentences, front-loaded with main purpose. Could add more detail without becoming verbose.

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

Completeness3/5

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

Description mentions output behavior if no outputPath, but lacks details on return format or structure. Adequate but not comprehensive.

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 covers 100% of parameters; description adds minimal extra meaning beyond schema (e.g., output formats already in enum). Baseline score appropriate.

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?

Description clearly states tool generates frontend code from DDS semantic data, supporting Vue 3 SFC and HTML. Distinct from sibling tools which are download/retrieve operations.

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?

Usage is implied (use when needing to generate code from DDS), but no explicit guidance on when not to use or alternatives among siblings.

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