Skip to main content
Glama

import_file

Imports 3D files into Blender from FBX, OBJ, GLTF/GLB, USD, STL, PLY, Alembic, or SVG, auto-detecting format from the file extension.

Instructions

Import a 3D file into Blender.

Supports FBX, OBJ, GLTF/GLB, USD, STL, PLY, Alembic (ABC), and SVG formats. Auto-detects format from file extension if type is empty.

Args: filepath: Absolute path to the file to import. Must exist. type: Optional format override. One of: FBX, OBJ, GLTF, USD, STL, PLY, ABC, SVG. Auto-detected from extension if empty.

Returns: Dict with imported file path and format.

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": {
      "filepath": "<filepath>"
    },
    "name": "import_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
filepathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "ABC",
      -  "DAE",
      -  "FBX",
      -  "GLTF",
      -  "OBJ",
      -  "PLY",
      -  "STL",
      -  "SVG",
      -  "USD",
      -  "X3D"
      -]New value: +[
      +  "ABC",
      +  "FBX",
      +  "GLTF",
      +  "OBJ",
      +  "PLY",
      +  "STL",
      +  "SVG",
      +  "USD"
      +]
  2. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / type / enum
      Added value: +[
      +  "ABC",
      +  "DAE",
      +  "FBX",
      +  "GLTF",
      +  "OBJ",
      +  "PLY",
      +  "STL",
      +  "SVG",
      +  "USD",
      +  "X3D"
      +]
  3. Changed1 schema field changedv1.2.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "title": "import_fileDictOutput",
      +  "type": "object"
      +}
  4. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add useful context: supported formats, format auto-detection, and the requirement that the file exist. It does not disclose import side effects—such as whether objects are added to the current scene or collection, how selection is affected, or what happens on failure—which is important for a scene-mutating operation.

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?

Front-loads the core action, then lists supported formats, then documents args and returns in a clean, scannable structure. Every sentence contributes useful information, and there is no filler.

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?

Covers format support, parameter behavior, path requirement, and a brief return description despite an output schema existing. It is nearly complete for a simple two-parameter import tool, with the main omission being scene-side effects of importing.

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

Parameters5/5

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

Schema description coverage is 0%, but the description fully documents both parameters: `filepath` is an absolute path that must exist, and `type` is an optional override with an explicit allowed-format list and auto-detection behavior. This adds all the meaning the schema lacks.

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?

States a specific verb and resource ("Import a 3D file into Blender") and enumerates the supported formats, so the agent knows exactly what the tool does. It does not explicitly distinguish itself from siblings like open_file or link_or_append, which keeps it from a 5.

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

Usage Guidelines3/5

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

Provides a clear usage rule for the `type` parameter: auto-detection from extension when empty, with a list of valid overrides. However, it gives no guidance on when to use this tool versus open_file, link_or_append, or export_file, and no when-not conditions.

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

Deploy Server

Other Tools