Skip to main content
Glama

mesh_cleanup

Run common cleanup operations to remove geometry issues and prepare 3D models for modeling, shading, or export.

Instructions

Run common mesh cleanup operations.

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": {
      "name": "<name>"
    },
    "name": "mesh_cleanup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it never says what is removed, whether the operation is destructive or reversible, or whether it acts on the named mesh object or the whole scene. 'Cleanup' implies geometry deletion without confirming consequences.

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

Conciseness2/5

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

The sentence is short and front-loaded but this is under-specification rather than conciseness; there is room for a clarifying clause that would cost little and help enormously.

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?

An output schema exists so return values need not be explained, but for a potentially destructive mesh tool with no annotations and an undocumented parameter, the description leaves the essential operational facts missing.

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

Parameters1/5

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

The single required parameter 'name' has 0% schema description coverage and the description adds no meaning: it could be an object name, a mesh datablock name, or even the name of a cleanup operation. The description does nothing to disambiguate it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Run common mesh cleanup operations" essentially restates the tool name without naming a single operation (merge by distance, delete loose, recalculate normals, fill holes). Among siblings like decimate_mesh and remesh_mesh, an agent cannot tell what mesh_cleanup actually changes on the mesh.

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?

There is no when-to-use guidance, no exclusion of alternatives such as decimate_mesh or remesh_mesh, and no statement of preconditions (selection state, edit vs object mode). The agent is left to infer entirely.

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