Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

open_project

Loads an existing Blender (.blend) file from disk, requiring confirmation before discarding unsaved changes and keeping embedded scripts disabled 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": "open_project"
  }
}

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 bears the full disclosure burden and does meaningful work: it warns that the current scene and datablocks are unloaded, states the confirmation gate for unsaved work, and notes that untrusted embedded scripts are disabled by default. It stops short of describing failure modes (missing path, corrupt file) or what the call returns on success.

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?

Four short sentences, each carrying distinct information: purpose, destructive warning, conditional requirement, security default. The WARNING is front-loaded immediately after the purpose statement, so a skimming agent cannot miss the destructive consequence.

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, five-parameter tool with no output schema, the description covers the three things an agent most needs: what gets destroyed, the confirmation gate, and the script-execution policy. Remaining gaps — return value and error behavior on invalid paths — are modest given the tool's straightforward load semantics.

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 the baseline would be 3, but the description adds a genuine cross-state dependency the schema does not encode: confirm_discard_unsaved is required only when the active scene has unsaved changes. It also reinforces the security default behind use_scripts. The deprecated 'approved' and 'task_id' parameters are left entirely to the schema.

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 opens with a specific verb and resource: 'Safely load and open an existing Blender (.blend) project file from disk,' including the file type and source. It does not, however, distinguish itself from the sibling 'open_blend_file', which an agent could plausibly confuse it with.

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?

A concrete precondition is given — 'Requires confirm_discard_unsaved=True if current scene has unsaved modifications' — which tells the agent when a particular call shape is mandatory. There is no statement of when to prefer this tool over the apparent sibling 'open_blend_file', and no exclusions, so routing guidance is only implied.

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