Skip to main content
Glama

blender_import

Import 3D models into Blender scenes from various formats including FBX, OBJ, GLTF, and CAD files. Supports automatic CAD conversion and mesh quality control.

Instructions

Import 3D files into Blender scenes.

Supports multiple operations through the operation parameter:

  • import_[format]: Import files in any supported format (FBX, OBJ, GLTF, STL, PLY, etc.)

  • import_cad: Import CAD files (STEP, STP, IGES, IGS) with automatic conversion

  • link_asset: Link external assets without importing

CAD IMPORT FEATURES:

  • Automatic STEP/STP conversion using Mayo, FreeCAD, or online tools

  • Mesh quality control (low/medium/high)

  • Scale adjustment for unit conversion

  • Direct integration with robotics-mcp CAD converter

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoImport operation typeimport_fbx
filepathNoPath to the file to import
file_formatNoFormat of the file (FBX, OBJ, GLTF, CAD, etc.)FBX
global_scaleNoGlobal scale factor for import
use_custom_normalsNoImport custom normals
import_shadingNoImport material shading
asset_nameNoLinkedAsset
cad_conversion_toolNoCAD conversion tool (auto, mayo, freecad, online)auto
mesh_qualityNoMesh quality for CAD conversion (low, medium, high)medium
cad_scale_factorNoScale factor for CAD unit conversion

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description reveals some behaviors like CAD conversion features and mesh quality control, but lacks information on side effects (e.g., impact on existing scene, overwriting). Since no annotations are provided, the description carries the full burden but leaves gaps.

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?

The description is well-structured with headings and bullet points, and front-loads the main purpose. While every sentence is relevant, it is slightly lengthy and could be more concise.

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?

Given the complexity (10 parameters, no required params) and the presence of an output schema, the description covers the main operations and features. However, it omits prerequisites (e.g., Blender must be running) and error handling details.

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 90%, so the baseline is 3. The description adds context for the operation parameter and CAD-related parameters, but does not provide significant new meaning beyond the schema for most parameters.

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?

The description clearly states the tool imports 3D files into Blender scenes and details multiple operations via the operation parameter, including specific format imports and CAD import. However, it does not explicitly differentiate from the sibling tool 'import_cad_file', which may cause confusion.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., blender_export, import_cad_file). There are no exclusions or recommendations for specific scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/blender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server