Skip to main content
Glama

3d-cad

cad_convert_to_stl

Convert OBJ, GLB (glTF 2.0), or 2D SVG (polygon extrusion) into Binary STL with unit scaling and voxel mesh decimation.

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": "cad_convert_to_stl"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoRaw OBJ or SVG text.
scaleNo
formatNo
inputPathNo
base64DataNo
outputPathNo
svgDepthMmNo
retentionPctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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, yet it says nothing about precedence when text, inputPath, and base64Data are all optional, whether a file is written to outputPath, or whether existing files are overwritten. Mentioning 'unit scaling' and 'voxel mesh decimation' hints at transformations but leaves their behavior unspecified.

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 dense sentence with zero filler, and the input formats and output type are front-loaded. It is efficient, though packing three formats plus two transformations into one clause makes it slightly hard to scan.

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?

With 8 mostly optional parameters, no annotations, no output schema, and 13% schema description coverage, the definition leaves too much unexplained for correct invocation, especially how to choose among text/inputPath/base64Data and what outputPath does. It is adequate to identify the tool but not to call it safely.

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 coverage is only 13% across 8 parameters, so the description must compensate; it does add meaning for scale (unit scaling), retentionPct (voxel mesh decimation), and svgDepthMm (polygon extrusion depth). However, the three alternative input sources (text, inputPath, base64Data) and outputPath remain semantically unexplained, which is the riskiest ambiguity for correct invocation.

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?

States a specific verb (convert) plus every accepted input format (OBJ, GLB/glTF 2.0, 2D SVG) and the exact output (Binary STL). The parenthetical '(polygon extrusion)' clarifies how SVG is handled, so an agent knows precisely what this tool does and produces.

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?

The description never says when to pick this over alternatives such as stl_heal or stl_slice_to_gcode, nor when a conversion is or isn't appropriate (e.g., already-STL input). Usage is only inferable from the accepted input formats.

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