Skip to main content
Glama

Import External Asset

blender_import_asset

Import 3D assets like FBX, OBJ, and GLTF files into Blender scenes with positioning, scaling, and optimization options for asset workflows.

Instructions

Import external 3D assets into Blender scene with comprehensive options.

Supports multiple 3D file formats including FBX, OBJ, GLTF, and more with advanced import options.

Args:

  • file_path (string): Path to asset file to import (relative to project)

  • format (optional): Asset format (auto-detected if not specified)

  • options (optional): Import options including location, rotation, scale, and processing

Returns: Import confirmation with object details and processing information

Examples:

  • Basic import: file_path="assets/models/chair.fbx"

  • With positioning: file_path="assets/tree.obj", options={location: [0, 0, 0]}

  • Optimized import: file_path="assets/vehicle.gltf", options={decimate: true, decimate_ratio: 0.5}

Use when: Adding external assets to scenes, importing models/textures, asset workflows Don't use when: Creating new primitives (use object creation tools instead)

Performance: Varies by file size and complexity, typically 1-10 seconds for most assets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to asset file to import
formatNoAsset format (auto-detected if not specified)
optionsNoImport options
Behavior4/5

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

The description adds valuable behavioral context beyond annotations: it discloses performance characteristics (1-10 seconds typical), lists supported file formats, and provides examples of usage patterns. While annotations cover basic safety (non-destructive, non-readonly), the description enhances understanding with practical implementation details.

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 clear sections (purpose, args, returns, examples, usage guidelines, performance). While comprehensive, some sections like the format list could be more concise. Overall, it's efficiently organized with most sentences adding clear value.

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

Completeness5/5

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

Given the tool's complexity (3 parameters with nested objects, no output schema), the description provides excellent contextual completeness. It covers purpose, usage guidelines, parameters, examples, performance expectations, and distinguishes from alternatives. The combination of description and schema provides everything needed for effective tool use.

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?

With 100% schema description coverage, the schema already documents all parameters thoroughly. The description adds minimal extra semantic value through the 'Args' section and examples, but doesn't provide significant additional meaning beyond what's in the structured schema. This meets the baseline for high schema coverage.

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 tool imports external 3D assets into Blender scenes with comprehensive options. It specifies the action (import), resource (external 3D assets), and context (Blender scene), and distinguishes itself from sibling tools like blender_create_primitive by focusing on external assets rather than internal creation.

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

Usage Guidelines5/5

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

The description includes explicit 'Use when' and 'Don't use when' sections, providing clear guidance on when to use this tool (adding external assets, importing models/textures) versus alternatives (object creation tools for primitives). This directly addresses sibling tool differentiation.

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/olbboy/claudekit-blender-mcp'

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