Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

import_scene

Imports 3D asset files such as glTF, FBX, USD, OBJ, STL, PLY, or ABC into the active Blender scene from an absolute file path.

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

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 exist, so the description carries the full behavioral burden, and it discloses almost nothing beyond the destination scene: not whether existing scene content is kept or replaced, what happens on a bad path or unsupported format, whether the operation is undoable, or how errors surface. The only behavioral hint is 'into the active Blender scene', which is thin for a mutating import.

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?

One short, front-loaded sentence with zero filler; the verb and effect precede the format enumeration.

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?

For an unannotated, scene-mutating import with no output schema, the definition is too thin: it omits side effects on the current scene, failure behavior, and any return/confirmation semantics that the agent would need to call it confidently.

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 coverage is 100%, so the schema already documents every parameter including format auto-detection, checksum verification, and the deprecated approved flag. The description's format list merely echoes the schema enum and adds no new parameter meaning, making baseline 3 appropriate.

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 concrete verb ('Imports') and resource ('3D asset file') and enumerates the supported formats plus the destination ('active Blender scene'). It never distinguishes itself from the similarly named sibling 'import_scene_asset', so an agent cannot tell the two apart from the text.

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, when-not-to-use, or prerequisite guidance. With a sibling literally called 'import_scene_asset', the absence of any routing information is a real gap.

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