Skip to main content
Glama

import_cad_file

Import STEP and IGES CAD files into Blender by converting them to mesh format for editing and rendering.

Instructions

Import CAD files (STEP, IGES) into Blender with automatic conversion.

This function handles the complete pipeline:

  1. Detect CAD file format

  2. Convert to mesh format using appropriate tool

  3. Import converted mesh into Blender

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filepathYesPath to CAD file
cad_formatNoCAD format (STEP, STP, IGES, IGS)STEP
global_scaleNoBlender import scale
mesh_qualityNoMesh quality (low, medium, high)medium
scale_factorNoCAD unit conversion scale
import_shadingNoImport material shading
conversion_toolNoConversion tool to use (auto, mayo, freecad, online)auto
use_custom_normalsNoImport custom normals

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

B3.3/5.0
Behavior2/5

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

Annotations are all false, providing no meaningful safety profile. The description outlines the conversion pipeline but does not disclose potential side effects, prerequisites, error behavior, or whether external tools/services are required. It adds procedural detail but lacks consequential transparency.

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 compact, front-loads the main purpose, and uses a numbered list for the pipeline. Every sentence contributes useful information without unnecessary verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is complex with a multi-step pipeline and 8 parameters, but the description covers only high-level steps. Prerequisites, mesh destination, and error cases are omitted. However, full schema parameter coverage and an output schema mitigate some gaps.

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?

All 8 parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds no extra parameter-level meaning, only referencing an 'appropriate tool' which maps to conversion_tool without clarifying distinctions like global_scale vs scale_factor.

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 the action ('Import CAD files') and specific formats (STEP, IGES), with a numbered pipeline that further defines the scope. This distinguishes it from generic import tools like 'blender_import'.

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. The pipeline is described, but there are no exclusions, conditions, or references to other import tools, leaving usage context only implied by the CAD-specific name.

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