Skip to main content
Glama
Shaolh0603

mcp-lanhu

by Shaolh0603
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

lanhu_design

Analyze Lanhu design drafts, extract design tokens, and download exportable slices from project URLs.

Instructions

Unified Lanhu design tool. Supports listing, analyzing, extracting tokens, and getting slices.

Modes:

  • list: List all designs in the project

  • analyze: Full design analysis with HTML+CSS, tokens, layers, and image (default)

  • slices: Extract slice/asset info for download

  • download: Download designer-marked exportable slices to a local directory and write a manifest.json mapping local files to CDN URLs

  • tokens: Extract design tokens only (fonts, colors, shadows, etc.)

For detailDetach URLs (contains image_id), pass design_names='all'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesLanhu project URL. Supports stage and detailDetach formats.
modeNoOperation mode. Default: analyze.analyze
includeNoContent to include in analyze mode. Default: ['html', 'tokens', 'layers', 'image']. Options: html, image (base64), tokens, layout, layers, slices.
layer_depthNoMaximum nested layer depth for analyze mode. 0 returns top-level layers only; use 'all' for the complete tree. Default: 4.
design_namesNoDesign name(s), index, or 'all'. Required for analyze/slices/tokens. Number = index from list, exact string = match by name or id.
download_dirNoDirectory to save slices in 'download' mode. May be absolute or relative to the server working directory. Only image files are written by default.
slice_name_mapNoOptional map from slice download-URL id (e.g. 'SketchPng8286fec') to a semantic asset name WITHOUT extension (e.g. 'list-header-bg'). Matched by prefix against the tail of each slice downloadUrl; applied to slices/download outputs as semanticName.
write_manifestNoWrite a manifest.json into download_dir. Default: false. Enable only when you need local-file ↔ CDN-URL tracking (e.g. replacing remote URLs during code generation).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose important behavioral traits: download persists files to a local directory and writes a manifest, analyze returns HTML+CSS/tokens/layers/image, and detailDetach URLs require design_names='all'. It omits auth/permission and error behavior, but the core side effects are covered.

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?

The description is well-structured with a front-loaded mode list and a prominent special-case note. Every sentence earns its place, and there is no redundant repetition of schema details.

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

Completeness4/5

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

For a complex tool with 8 parameters, nested objects, and no output schema, the description covers the modal behaviors and roughly indicates outputs. The schema supplies parameter details, and the special URL note fills a critical gap. Some return-format and edge-case details remain unspecified, but the tool is largely selectable and invocable.

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% and each parameter already has a rich description, so the description adds little beyond the schema. The detailDetach/design_names note is useful extra guidance, but most parameter semantics live in the schema, keeping this at the baseline.

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 states a specific resource (Lanhu design) and enumerates five concrete operations (list, analyze, slices, download, tokens), making the tool's purpose clear. While the opening 'Unified Lanhu design tool' is somewhat generic, the mode list grounds it and differentiates it from the sibling tools focused on invite links and pages.

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?

The description gives clear mode-level guidance, including which mode is the default (analyze) and what each mode is for (e.g., download saves files and writes a manifest). It also provides a specific conditional rule for detailDetach URLs. However, it does not explicitly mention sibling alternatives or when to avoid this tool.

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