formlabs-local-mcp

import_model

Import a 3D model file (STL, OBJ, 3MF, STEP) into a PreForm scene for printing, with automatic repair and unit handling. Returns the model ID for further operations.

Instructions

Import a model file (STL, OBJ, 3MF, STEP) into a scene. file must be an absolute path. Returns the model with its id. Defaults differ from the raw API: repair_behavior=REPAIR (the API default ERROR fails on slightly broken meshes most CAD tools export) and units=MILLIMETERS (use INCHES for inch files, DETECTED to let PreForm guess). After importing, the scene is re-read and the call fails with IMPORT_PRODUCED_EMPTY_SCENE if no model was added: the file is malformed, do not retry.

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

Input Schema

Name	Required	Description	Default
`file`	Yes
`name`	No
`scale`	No
`units`	No		MILLIMETERS
`position`	No
`scene_id`	No	Scene id; omit for the default scene	default
`orientation`	No	Euler degrees {x,y,z}, or {z_direction:[..], x_direction:[..]} unit vectors
`repair_behavior`	No		REPAIR
`split_multi_model_file`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4Sep 16, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Discloses defaults that differ from the raw API, the post-import scene re-read, and the exact failure mode IMPORT_PRODUCED_EMPTY_SCENE with a 'do not retry' instruction. This is substantial behavioral context beyond the basic readOnly/destructive annotations.

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?

Four sentences, each adding essential information: purpose, path requirement, default/unit guidance, and failure behavior. No filler, and the most important constraints are front-loaded.

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 9-parameter tool with no output schema, the description covers the core workflow, output shape, and a critical failure mode. It is not fully complete because some parameter semantics are absent, but combined with the schema it gives an agent enough to call the tool successfully.

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 only 22%, and the description compensates for file, units, and repair_behavior with meaningful guidance. However, it leaves several parameters (name, scale, position, split_multi_model_file) unexplained, so it only partially bridges the coverage gap.

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?

The first sentence names the action (import), the resource (model file), supported formats (STL, OBJ, 3MF, STEP), and target (scene), and the return value (model with id). This makes it easy to distinguish from sibling model operations even without naming them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage constraints: file must be absolute, units should be INCHES for inch files or DETECTED to let PreForm guess, and malformed files should not be retried. It does not explicitly name alternative tools, so it falls short of a 5, but the context is clear.

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