Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

import_scene_asset

Import 3D asset files (glTF/GLB, FBX, USD, OBJ, STL, PLY, ABC) into the active Blender scene, with optional auto-detection and checksum verification.

Instructions

Imports a 3D asset file (glTF/GLB, FBX, USD/USDC/USDA, OBJ, STL, PLY, ABC) into the active Blender scene.

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_scene_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoFile format: 'GLTF', 'GLB', 'FBX', 'USD', 'USDC', 'USDA', 'OBJ', 'STL', 'PLY', 'ABC'. Auto-detected from file extension if omitted.
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
filepathYesAbsolute path to existing 3D asset file on disk.
verify_checksumNoWhether to verify asset integrity against a SHA-256 sidecar file if present. Defaults to False.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only implies mutation by saying objects land in the "active Blender scene." It does not say whether existing objects are affected, whether imports are additive or replace content, what happens with duplicate names, or what the tool returns or raises on failure.

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 front-loaded sentence with the action and destination stated immediately, which is well structured for a quick scan. The parenthetical format list is somewhat redundant with the schema enum and costs space without adding information.

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

Completeness2/5

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

This is a scene-mutating tool with no annotations and no output schema, so the description must explain side effects and results, and it does not. An agent cannot tell from the definition whether the import adds objects to the selection, how errors surface, or whether the operation is undoable.

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?

Schema description coverage is 100%, so filepath, format, task_id, approved, and verify_checksum are already documented, and the description's format list merely restates the enum. It adds no meaning about the deprecated approved flag or the checksum sidecar behavior beyond what the schema states, so the baseline of 3 applies.

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?

The description uses a specific verb ("Imports") plus a concrete resource ("3D asset file") with an enumerated format list and an explicit destination ("active Blender scene"). It does not, however, distinguish itself from the sibling import_scene, leaving the agent to infer that this one targets asset files rather than whole scenes.

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 guidance on when to choose this over import_scene or export_scene_asset, and no stated prerequisites such as an open/active scene or the file needing to exist on disk. The agent must infer the calling context entirely from the sentence.

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