Resolve an invite link into the actual Lanhu project URL by extracting tid, pid, and docId parameters, enabling direct access to the design source.
Resolve Lanhu invite/share link to actual project URL with tid/pid/docId parameters.
| Name | Required | Description | Default |
|---|---|---|---|
| invite_url | Yes | Lanhu invite link. Example: https://lanhuapp.com/link/#/invite?sid=xxx |
Changes observed during successful MCP inspections.
v2.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must cover behavioral traits. It explains the transformation (resolve invite link to URL with parameters) but does not mention any side effects, authentication needs, or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence that is concise and front-loaded with the key action. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple tool with one parameter and no output schema, the description is adequate but lacks detail on the resolved URL format or potential errors (e.g., invalid link).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and includes an example. The description does not add further meaning beyond what the schema provides, so baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool resolves a Lanhu invite/share link to an actual project URL with parameters, distinguishing it from sibling tools that likely handle design or page operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool vs alternatives, but the purpose implies it's for converting invite links, which is a distinct use case from lanhu_design and lanhu_page.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.