Skip to main content
Glama

execute_blender_code_for_cli

Destructive

Execute trusted Python code in a fresh background Blender process against a specified .blend file to automate scene tasks or run headless scripts.

Instructions

Run trusted Python in a fresh background Blender process on the specified blend file.

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

Input Schema

NameRequiredDescriptionDefault
codeYes
timeoutNo
blend_fileYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations declare destructiveHint=true and readOnlyHint=false; the description does not contradict this. It adds genuinely useful context that execution occurs in a fresh background process, which implies isolation from the interactive session, but it is silent on whether results are saved back to the blend file, what happens on timeout, and what 'trusted' means operationally.

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?

A single front-loaded sentence with no filler; the key differentiator (fresh background process) appears early. Slightly terse given the amount of undocumented behavior, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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. However, for a destructive code-execution tool with 0% schema parameter coverage, the definition should at minimum explain the timeout and whether blend-file mutations persist; those gaps leave it only marginally adequate.

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 3 parameters, so the description must carry the semantics and largely does not. It gestures at 'blend_file' (specified blend file) and 'code' (Python), but the 'timeout' parameter, including its default and units, is never mentioned anywhere.

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 names a specific verb ('Run') and resource ('Python') and adds the differentiator that execution happens in a fresh background Blender process against a specified blend file. It is clearly distinguishable from the in-session 'execute_blender_code' sibling by the 'fresh background process' qualifier, though it never names that sibling explicitly.

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?

"Trusted Python" and "fresh background process" imply when this is appropriate (isolated, non-interactive execution), but there is no explicit when-to-use/when-not guidance and no reference to the sibling tools it competes with. The agent must infer selection criteria from the word 'trusted'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.