Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

open_blend_file

Load an existing Blender .blend project from disk, replacing the current scene and discarding unsaved changes only when confirmed. Embedded Python scripts stay disabled unless explicitly allowed.

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": "open_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.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and it does so well: it warns that the call unloads the current scene and datablocks, states the confirmation flag needed when there are unsaved changes, and notes that embedded scripts are disabled by default. It omits failure behavior and whether the operation is reversible, which keeps it from a 5.

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?

Three dense sentences, front-loaded with the action, then the destruction warning, then the security default. Every sentence earns its place with no restatement of schema fields.

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 load with no annotations and no output schema, the description covers the essential risks: data loss, the confirmation gate, and script execution policy. It falls short on what the tool returns after opening and how it relates to the near-duplicate sibling tools.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning beyond the schema: it explains the conditional trigger for confirm_discard_unsaved (only when unsaved modifications exist) and reinforces the security default on use_scripts. It does not address the deprecated approved flag or task_id, but those are already documented.

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: 'Safely load and open an existing Blender (.blend) project file from disk.' That is unambiguous about what the tool does. However, it offers no differentiation from the closely named siblings load_blend_file and open_project, so an agent must guess how they differ.

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?

The description supplies a real precondition ('Requires confirm_discard_unsaved=True if current scene has unsaved modifications'), which is conditional usage information. But it never says when to pick this over load_blend_file or open_project, and there is no explicit when-not guidance.

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