Skip to main content
Glama

3d-cad

stl_heal

Repair non-manifold open holes, degenerate facets, and inverted surface normals in an STL mesh.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stl_heal"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathNoLocal path to STL file (stdio MCP).
base64DataNoBase64-encoded ASCII or Binary STL (remote MCP).
outputPathNoOptional local output path for healed Binary STL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 behavioral burden, and it does not say whether the input file is modified in place or left untouched, what happens when outputPath is omitted, whether a missing output is written elsewhere, or what the tool returns (no output schema exists either). For a mutating file-repair operation that is a meaningful gap.

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

Conciseness4/5

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

A single tight sentence with the defect list front-loaded and zero filler. It could have been structured to also carry the input/output mode distinction, but nothing present is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The schema fully documents the three parameters, so the missing piece is behavioral: in-place vs file output, error behavior on unrepairable meshes, and return shape. With no annotations and no output schema, the description should do more than name the defects it fixes.

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?

Schema description coverage is 100%, with inputPath, base64Data, and outputPath each individually documented in the schema (including the stdio vs remote MCP distinction). The description adds no parameter meaning beyond that, so the baseline 3 applies.

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

Purpose4/5

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

Specific verb ('Repair') plus resource ('STL mesh') plus enumerated defect classes (non-manifold open holes, degenerate facets, inverted normals), which tells an agent exactly what class of problem this fixes. It does not name or differentiate itself from any sibling, so it stops short of a 5.

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?

Usage is only implicit: an agent must infer that it should call this when an STL fails downstream operations due to the listed defects. There is no explicit when-to-use, no when-not-to-use, and no mention of upstream tools like cad_convert_to_stl or downstream ones like stl_slice_to_gcode.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources