Cleans up mesh geometry by recalculating normals, merging vertices by distance, dissolving degenerate elements, and applying smooth shading with angle-based auto smooth.
网格清理：重算法线、按距离合并顶点、溶解退化、平滑着色、按角度自动平滑（弧度）。
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| inside | No | ||
| threshold | No | ||
| shade_smooth | No | ||
| recalc_normals | No | ||
| auto_smooth_angle | No | ||
| merge_by_distance | No | ||
| dissolve_degenerate | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description lists the actions performed but does not disclose consequences such as destructive modifications, potential loss of UVs or materials, or whether the operation is reversible. Without annotations, the description fails to fully convey the tool's behavioral impact.
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?
The description is a single, compact sentence that efficiently enumerates all core operations. No redundant words or unnecessary detail, making it highly concise and well-structured.
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 tool has 8 parameters and no annotations or output schema, the description is too sparse. It omits essential context such as default behaviors, side effects on the mesh, or any prerequisites, leaving the agent without enough information to invoke it correctly in varied situations.
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?
The description adds some parameter context by mentioning 'by distance' for merge and 'radians' for auto smooth angle, which clarifies threshold units and angle format. However, it does not explain the effect of each boolean parameter or the meaning of the required 'name' parameter beyond the schema.
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 lists the mesh cleanup operations: recalculate normals, merge vertices by distance, dissolve degenerate, smooth shading, and auto smooth by angle. This gives a specific and actionable sense of the tool's purpose, distinguishing it from generic mesh modification tools.
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 guidance is provided on when to use this tool versus alternatives like check_mesh or apply_modifier. The description does not mention prerequisites, scenarios, or conditions under which cleanup is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.