Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

execute_blender_code

Safely execute structured Blender modeling operations or AST-validated Python code with explicit human approval and automatic undo rollback on failure.

Instructions

Safely execute structured modeling operations or restricted AST-validated Blender Python code. All mutations require explicit trusted human approval in Blender and execute transactionally with automatic undo rollback on failure. Unrestricted eval/exec is prohibited. Supports operations: 'add_modifier', 'modify_modifier', 'remove_modifier', 'set_shade_mode', 'subdivide_mesh', 'create_material', 'assign_material', 'parent_object', 'join_objects'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "execute_blender_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoOptional Python modeling script strictly restricted to allowlisted bpy operations. Must pass static AST security validation.
task_idNoOptional task or workflow identifier for grouping related scene mutation operations.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent. Mutations must be approved through a trusted approval mechanism.
operationsNoList of structured modeling operations to execute sequentially within a single transaction.
transactionalNoWhether to wrap execution in a Blender undo transaction to roll back on any error. Defaults to True.

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 present, the description carries the behavioral burden and does so well: it discloses that all mutations require explicit trusted human approval inside Blender, that execution is transactional with automatic undo rollback on failure, and that code must pass static AST security validation. It stops short of describing return values, partial-failure reporting, or whether any read-only code paths exist.

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 followed by an action list; the safety and transactional guarantees are front-loaded before the enumeration. Every sentence adds information, though the trailing action list partially duplicates the schema enum.

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 five-parameter, high-risk mutation tool with no annotations and no output schema, the definition covers approval, validation, and rollback adequately. It is still incomplete on what a successful call returns and how errors from a mid-list failure are surfaced to the caller.

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 enum of actions and the params dictionary are already documented in the input schema, making 3 the baseline. The description reinforces the action list and adds the sequencing/transaction semantics ('operations ... sequentially within a single transaction'), but supplies no new meaning for code, task_id, or approved beyond what the schema states.

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 ('execute structured modeling operations or restricted AST-validated Blender Python code') and enumerates the nine supported actions, so the agent knows exactly what capability is offered. It does not, however, distinguish itself from siblings such as apply_modifier, create_material, or assign_material that overlap with the listed 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?

The description implies usage through constraints: mutations need trusted human approval, and unrestricted eval/exec is prohibited, which narrows when this tool is appropriate. But it never states when an agent should pick this tool over the many single-purpose siblings, leaving the routing decision to inference.

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