Skip to main content
Glama

blender_import

Import 3D and CAD files into Blender scenes. Supports multiple file formats, mesh quality control, and asset linking for flexible asset integration.

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations only contain false flags, so the description carries the burden. It adds useful context like automatic STEP/STP conversion with Mayo/FreeCAD/online tools and direct integration with robotics-mcp CAD converter, but it does not disclose side effects on the scene or potential failure modes.

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?

The description is well-structured with a front-loaded purpose statement, bullet lists for operations and CAD features, and no redundant or filler content. Each line adds meaningful detail.

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 tool's complexity (10 parameters, output schema exists), the description covers operations and CAD specifics adequately. It does not mention prerequisites like an active Blender session, but the output schema and detailed operation list make it sufficiently complete for an agent to select and invoke.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (90%), but the description enriches the operation parameter by enumerating possible values (import_[format], import_cad, link_asset) and explains the purpose of mesh_quality, cad_scale_factor, and cad_conversion_tool in the CAD features section.

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 description clearly states 'Import 3D files into Blender scenes' and elaborates with specific operations (import_[format], import_cad, link_asset). This distinguishes it from related tools like blender_export and provides a clear scope.

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 lists operation types within the tool but gives no explicit guidance on when to use this tool versus alternatives such as import_cad_file or blender_export. There are no exclusions or comparisons to siblings.

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

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