Skip to main content
Glama

import_asset

Imports 3D assets in FBX, OBJ, STL, GLTF, GLB, USD, or BLEND format into Blender, optionally placing them in a specified collection.

Instructions

Import a 3D asset (FBX/OBJ/STL/GLTF/GLB/USD/BLEND).

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": {
      "path": "<path>"
    },
    "name": "import_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
collectionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and delivers little. It does not say whether the import mutates the scene, whether it creates a new collection, what happens on name collisions, or where the asset lands; the format enumeration is the only real disclosure.

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?

A single tight sentence with the resource and the format enumeration front-loaded and no wasted words. Its brevity is genuine conciseness rather than under-specification padding.

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?

An output schema exists, so return-value explanation is not needed, and the format list covers the main ambiguity about supported files. However, for a scene-mutating import tool with zero annotations and an undocumented `collection` parameter, the definition leaves meaningful gaps an agent would need to probe at call time.

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

Parameters2/5

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

Both parameters have 0% schema description coverage, so `collection` is entirely undocumented in both schema and description — an agent cannot know whether it names a target collection, an existing one, or creates one. The format list at least implies what file extensions `path` accepts, but that is only partial compensation.

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?

A specific verb ("Import") plus resource ("3D asset") and an explicit list of supported formats gives an agent a clear picture of what the tool does. It stops short of distinguishing itself from the sibling tools import_external_asset and import_polyhaven_via_blender, so an agent facing those alternatives gets no help choosing.

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?

There is no when-to-use guidance and no mention of alternatives, despite three import-related siblings in the catalog. The only usage signal is the implied one from the verb "Import" and the format list, leaving the agent to infer whether this is for local files versus provider-backed imports.

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