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

lanhu-mcp-codex

by Kforward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Parse Lanhu URL

lanhu_parse_url
Read-only

Extract pid, tid, image_id, doc, and route from a Lanhu project or design URL. Provides structured design context for AI agents.

Instructions

Parse a Lanhu project/design URL into pid, tid, image_id, doc and route fields.

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

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The description aligns with the readOnlyHint annotation, indicating a non-destructive operation. It adds value by detailing the extracted fields, which goes beyond what annotations provide. No contradictions found.

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 a single, concise sentence that front-loads the action and output, efficiently conveying all necessary information without any extraneous text.

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?

Given the tool's simplicity (single parameter, no output schema), the description is complete. It fully explains what the tool does and what it returns, leaving no ambiguity for the agent.

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

Parameters4/5

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

The input schema only specifies type and minLength for the 'url' parameter with no description. The tool's description clarifies that the URL should be a Lanhu project/design URL, providing meaningful context for the parameter's expected content.

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 action ('Parse a Lanhu project/design URL') and its output components ('pid, tid, image_id, doc and route fields'), making its purpose very specific and distinct from sibling tools like getting design context or listing images.

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 when you have a Lanhu URL and need to extract its parts, but it does not provide any explicit guidance on when to use this tool over alternatives, nor does it mention any prerequisites or limitations.

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