Skip to main content
Glama

execute_blender_code

Execute Python code inside Blender to automate 3D tasks such as modeling, shading, lighting, animation, and rendering when script permissions allow.

Instructions

Execute Python code inside Blender when script permissions allow it.

    Warning: this is not a secure sandbox. It can access files, network, and
    system capabilities available to the Blender process.
    

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": {
      "code": "<code>"
    },
    "name": "execute_blender_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
timeoutNo
confirmedNo
preview_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does valuable work disclosing that this is 'not a secure sandbox' with file, network, and system access — an important risk signal — but it says nothing about the timeout, the confirmed flag, or preview_only, all of which materially change what happens when the tool runs.

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?

Two short blocks: the capability first, then a prominent warning. Every sentence earns its place and the risk disclosure is not buried.

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?

An output schema exists, so return values need not be described. But for an arbitrary-code-execution tool with four undocumented parameters and no annotations, the definition omits critical operational detail: whether execution proceeds without confirmed, what preview_only returns, and what a timeout does to the running script.

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

Parameters2/5

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

Schema description coverage is 0% across 4 parameters, so the description must compensate and it largely does not. 'Code' is implicitly explained by the verb, but timeout, confirmed, and preview_only — two of which appear to be safety/approval controls — receive no explanation of their semantics or effects.

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 Python code inside Blender') plus a scoping condition ('when script permissions allow it'). It is clearly distinguishable from the task-specific siblings (add_modifier, capture_render, etc.), though it never explicitly says it is the general-purpose escape hatch when no dedicated tool fits.

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?

The only guidance is the precondition 'when script permissions allow it', which is a gating condition rather than when-to-use guidance. There is no statement about when to prefer the dedicated Blender tools, when this is inappropriate, or whether confirmation is required before execution.

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