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

lanhu-mcp-codex

by Kforward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Generate Lanhu Design Context

lanhu_get_design_context
Read-only

Extracts design context from a Lanhu URL into local context.md, context.json, and optional thumbnail files for AI agents.

Instructions

Generate local context.md/context.json and optional thumbnail files from a Lanhu URL.

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_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
outputDirNo
includeImagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The description claims to generate local files, which may contradict the readOnlyHint=true annotation (generating files is a side effect). It fails to clarify authentication needs, rate limits, or whether this modifies server state.

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

Conciseness3/5

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

The single sentence is concise and front-loaded, but it is overly brief, sacrificing clarity and completeness. It could include more detail without becoming verbose.

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

Completeness2/5

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

With 3 parameters and no output schema, the description fails to explain output directory, the nature of 'context', or the output format. It is insufficient for correct tool usage.

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

Parameters2/5

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

0% schema description coverage means the description must explain parameters. It only relates 'from a Lanhu URL' to the url parameter, and hints at thumbnail generation without naming includeImages. outputDir is completely omitted.

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 action: generate local context files and optional thumbnails from a Lanhu URL. It uses a specific verb-resource pair and distinguishes from siblings like listing images or parsing URLs.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings or alternatives. It neither specifies prerequisites nor provides context for appropriate invocation.

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