Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

load_blend_file

Safely open an existing Blender .blend file from disk, unloading the current scene and datablocks. Requires confirmation to discard unsaved changes and blocks embedded scripts by default.

Instructions

Safely load and open an existing Blender (.blend) project file from disk. WARNING: Unloads current scene and datablocks. Requires confirm_discard_unsaved=True if current scene has unsaved modifications. Disables untrusted embedded scripts by default.

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

Input Schema

NameRequiredDescriptionDefault
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
filepathYesAbsolute filesystem path to the target .blend file to open.
use_scriptsNoWhether to allow embedded Python scripts in the opened file (defaults to False for security).
confirm_discard_unsavedNoExplicit confirmation to discard any unsaved modifications in the active project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it warns that the current scene and datablocks are unloaded (destructive side effect), states the confirmation gate for unsaved work, and discloses that embedded Python scripts are disabled by default. It stops short of describing failure modes or what the tool returns on error.

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?

Three tight sentences, with the destructive consequence front-loaded immediately after the purpose. Minor redundancy in 'load and open' and 'Safely' does little work, but nothing is padded.

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?

For a destructive, no-annotation tool with a rich schema, the description covers the critical risks: data loss, the confirmation gate, and the script-security default. The remaining gaps are the unaddressed overlap with open_blend_file and the absence of any return or error behavior, which matter somewhat given there is no output schema.

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 all five parameters including defaults and the untrusted-status of 'approved'. The description adds modest value by tying confirm_discard_unsaved to the unsaved-modifications condition and reinforcing the use_scripts default, but most parameter meaning lives in the schema, so the baseline 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?

States a specific verb and resource: load/open an existing Blender .blend file from disk. Clear on its own, but it never distinguishes itself from the sibling open_blend_file, leaving an agent unable to choose between two apparently identical operations.

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 conditional prerequisite ('Requires confirm_discard_unsaved=True if current scene has unsaved modifications'), which is real usage guidance. However, there is no statement of when to prefer this over open_blend_file or save_blend_file, and no guidance on the deprecated 'approved' flag, so routing must be inferred.

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