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

lanhu-mcp-server

by DC911360
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

lanhu_get_designs

Fetches design drafts from a specified Lanhu project to support automated design-to-code generation.

Instructions

获取项目下的设计稿列表。使用项目的 UUID（sourceId）作为 projectId。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lanhu_get_designs"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdNo项目 UUID（sourceId），不传则使用配置的默认项目

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It reveals basic read-only behavior (listing designs) but lacks details on pagination, sorting, filtering, or response format. For a simple list tool, this is adequate but not comprehensive.

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 short, front-loaded sentences with no redundant information. Every sentence adds value: first states purpose, second clarifies parameter usage.

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?

Given no output schema and simple input, the description covers purpose and parameter but omits details about the list contents, pagination, or other results. It is minimally complete but leaves gaps for an 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% with one parameter fully described. The description adds context (sourceId, default project) but largely mirrors the schema's description. Baseline 3 is appropriate as it adds marginal value.

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 the tool retrieves a list of designs under a project, specifying the use of project UUID as parameter. This distinguishes it from sibling tools like lanhu_get_design_detail (single design) or lanhu_download_* (downloads).

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?

Description explains how to use the parameter (use project UUID) and that it defaults to a configured project if omitted. However, it does not explicitly state when to use this tool vs alternatives like lanhu_get_design_detail or lanhu_list_projects.

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