Skip to main content
Glama
ZachHandley

blender-mcp-enhanced

by ZachHandley

execute_blender_code

Execute Python code in Blender with shared context for persistent workflow across multiple steps.

Instructions

Execute arbitrary Python code in Blender. Make sure to do it step-by-step by breaking it into smaller chunks.

Now includes shared context between executions! You can use:
- shared['variable_name'] = value  # Store variables for later use
- get_object('handle_name')       # Get stored object references
- get_material('handle_name')     # Get stored material references
- store_object('handle', 'obj_name')    # Store object reference
- store_material('handle', 'mat_name')  # Store material reference

Parameters:
- code: The Python code to execute

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
Behavior2/5

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

No annotations are provided, so the description must disclose all behavioral traits. It mentions shared context but does not describe potential side effects, security implications, or error handling, which are critical for a code execution tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat verbose with the shared context explanation and could be more concise. It front-loads the main action but includes a long list of helper functions.

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?

For a code execution tool, the description covers basic usage and shared context, but lacks details on return values, error behavior, or limitations. No output schema is present, increasing the need for description completeness.

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 description coverage is 0%, but the description explains that 'code' is Python code and provides examples of shared context usage. However, it does not add significant meaning beyond the parameter name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it executes arbitrary Python code in Blender, with step-by-step guidance and shared context. It distinguishes from siblings like execute_context_script by emphasizing arbitrary code.

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 provides a guideline to break code into smaller chunks, but lacks explicit when-to-use or when-not-to-use guidance, and does not mention alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ZachHandley/blender-mcp-enhanced'

If you have feedback or need assistance with the MCP directory API, please join our Discord server