Skip to main content
Glama

execute_blender_code

Run Python code directly in Blender to automate 3D modeling tasks, manipulate scenes, control materials, and integrate assets through step-by-step execution.

Instructions

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

Parameters:

  • code: The Python code to execute

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes

Implementation Reference

  • The main handler function for the 'execute_blender_code' tool. It connects to Blender via a persistent socket connection, sends the provided Python code to Blender using the 'execute_code' command, and returns the execution result or error message.
    @mcp.tool()
    def execute_blender_code(ctx: Context, code: str) -> str:
        """
        Execute arbitrary Python code in Blender. Make sure to do it step-by-step by breaking it into smaller chunks.
        
        Parameters:
        - code: The Python code to execute
        """
        try:
            # Get the global connection
            blender = get_blender_connection()
            result = blender.send_command("execute_code", {"code": code})
            return f"Code executed successfully: {result.get('result', '')}"
        except Exception as e:
            logger.error(f"Error executing code: {str(e)}")
            return f"Error executing code: {str(e)}"
  • The @mcp.tool() decorator registers the execute_blender_code function as an MCP tool.
    @mcp.tool()
  • The function signature and docstring define the input schema (ctx: Context, code: str) and output (str).
    def execute_blender_code(ctx: Context, code: str) -> str:
        """
        Execute arbitrary Python code in Blender. Make sure to do it step-by-step by breaking it into smaller chunks.
        
        Parameters:
        - code: The Python code to execute
        """
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Execute arbitrary Python code' but fails to cover critical traits like safety implications (e.g., potential for destructive changes, permissions required), performance aspects (e.g., execution time limits, error handling), or output behavior. This leaves significant gaps for a tool that executes code.

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?

The description is appropriately sized with two sentences and uses a bullet point for the parameter, making it front-loaded and efficient. However, the second sentence ('Make sure to do it step-by-step...') could be more precise, slightly reducing conciseness.

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?

Given the complexity of executing arbitrary code, no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks essential details like what the tool returns, error conditions, or safety warnings, making it inadequate for such a potentially powerful tool.

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?

The description adds minimal semantics by stating 'code: The Python code to execute', which matches the single parameter in the schema. With 0% schema description coverage, this provides some value, but it doesn't compensate fully (e.g., no details on code format, constraints, or examples). The baseline is 3 due to the single parameter, but it's not enhanced significantly.

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 clearly states the verb 'Execute' and the resource 'arbitrary Python code in Blender', making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its siblings (like other execution or modeling tools), which prevents a perfect score.

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 description provides minimal guidance with 'Make sure to do it step-by-step by breaking it into smaller chunks', which is vague and doesn't specify when to use this tool versus alternatives (e.g., other execution or import tools in the sibling list). No explicit when/when-not or alternative tools are mentioned.

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/wenyen-hsu/blender-mcp'

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