Lanhu MCP

Overview Schema Source Related Servers Discussions Admin

lanhu_inspect_design

Inspect a prepared design packet to retrieve summaries, trees, nodes, assets, slices, or Unity plans. Use views and filters to extract the exact UI details needed for UGUI prefab generation.

Instructions

Inspect a prepared design packet through a compact task-oriented view.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`view`	No	Information view to return.	summary
`node_ids`	No	Node ids required by the nodes view.
`max_depth`	No	Maximum hierarchy depth for tree view.
`packet_id`	Yes	Packet id returned by lanhu_prepare_design.
`include_style`	No	Include style/text fields in tree view.
`component_policy`	No	Interactive component generation policy for Unity plan.	conservative
`include_reference`	No	Include the full design reference in slices or Unity plan.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 21, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'Inspect' implies a read-only operation, but the description does not explicitly state whether the packet is modified, what data is returned, or that different views may have different computation costs. It adds some context with 'compact task-oriented view' but little detail about side effects or behavior.

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, focused sentence with no redundant wording. It front-loads the core action and object, and every part contributes to the agent's understanding of the tool's purpose.

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?

Given that an output schema exists and all parameters are fully documented in the schema, the description does not need to explain return values or parameter details. The main gap is the lack of explicit guidance on when to use this tool versus list/prepare/generate, but the overall context from the schema and sibling names is sufficient for an agent to operate correctly.

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?

The input schema has 100% description coverage, with each parameter including a meaningful description and defaults/enums documented. The tool description itself adds no additional parameter semantics, so the baseline of 3 is appropriate.

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 uses the specific verb 'Inspect' with the resource 'prepared design packet' and 'compact task-oriented view', clearly distinguishing this tool from siblings like lanhu_prepare_design or lanhu_generate_unity_prefab. The scope is clear enough for an agent to know exactly what the tool does.

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 phrase 'prepared design packet' and the packet_id schema description 'returned by lanhu_prepare_design' convey that this tool should be used after preparation. It does not explicitly enumerate when-not-to-use or name alternatives, but the inspection-vs-preparation/generation distinction is evident from sibling names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server