Skip to main content
Glama

convert_3d

Transform 3D model files between OBJ, STL, PLY, GLB, GLTF, OFF, and 3MF formats, with optional scaling and unit conversion. Outputs OBJ, STL, PLY, GLB, GLTF, or JSON for further processing.

Instructions

Convert 3D model files. Input: obj, stl, ply, glb, gltf, off, 3mf. Output: obj, stl, ply, glb, gltf, json. Built-in obj/stl/ply→json; other formats require blender or assimp CLI.

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": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "convert_3d"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoScale factor (optional)
unitsNoTarget units: mm, cm, m, in (optional)
inputPathYesAbsolute path to input 3D model file
outputPathYesAbsolute path for output file (include extension)
inputFormatNoInput format (auto-detected if not provided)
outputFormatNoOutput format (auto-detected if not provided)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose one important non-obvious behavior: the dependency on external tooling (blender or blender/assimp CLI) for most format pairs, which is a genuine runtime-failure signal. It says nothing about overwrite behavior when outputPath already exists, whether the call is synchronous/blocking, typical conversion time, or error reporting, all of which matter for a file-mutating tool with zero annotation coverage.

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?

Three short sentences in a compact Input/Output/Constraint ledger format with the essential caveat last. No filler, and the format contract is front-loaded where the agent will read it first.

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?

For a 6-parameter conversion tool with a fully documented schema and no output schema, the description covers the format matrix and the critical built-in-vs-external dependency, which is the main thing that could surprise an agent. Minor gaps remain around overwrite semantics and failure modes, but nothing essential to invoking it correctly is missing.

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%, so the schema already documents every parameter including the two enums and their auto-detection defaults, making 3 the baseline. The description's format lists merely restate the enum values and add no semantics for scale or units (e.g., how units interact with scale, whether they rescale geometry or just relabel).

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?

Opens with a specific verb+resource ("Convert 3D model files") and immediately bounds the domain with explicit input and output format lists, which cleanly separates it from the other convert_* siblings (audio, video, image, etc.). It stops short of a 5 only because it never names a sibling or states the boundary explicitly; the differentiation is inferred from the media type.

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?

The line "Built-in obj/stl/ply→json; other formats require blender or assimp CLI" is real, actionable guidance about which invocations will succeed natively versus need external binaries, and it implies a failure condition. However, there is no guidance on when to use this versus batch_convert (multiple files) or get_supported_formats, and no stated prerequisites for installing/pointing at the blender or assimp CLI.

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