Skip to main content
Glama

blender_exec

Execute Python scripts within Blender to automate 3D content creation, query scene data, and control the software remotely through the MCP Bridge.

Instructions

Execute a Python script inside Blender.

IMPORTANT RULES:
- The script MUST define a main() function and call it
- Use send_status("message") to report progress
- Use bpy.data.* APIs instead of bpy.ops.* when possible
- Script MUST terminate - no infinite loops
- Catch exceptions and handle errors gracefully

Args:
    script: Python code to execute in Blender. Has access to 'bpy' and 'send_status()'.

Returns:
    JSON string with execution results including status and any messages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scriptYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/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 thoroughly describes execution rules (e.g., script structure, API preferences, termination requirements, error handling) and return format (JSON string with status and messages), adding significant value beyond what the input schema provides.

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?

The description is appropriately sized and front-loaded, starting with the core purpose followed by structured rules and parameter details. Every sentence earns its place by providing essential information without redundancy, making it efficient and well-organized.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (executing scripts in an external environment), lack of annotations, and presence of an output schema (which covers return values), the description is complete. It addresses purpose, rules, parameters, and behavioral expectations, leaving no significant gaps for the agent.

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

Parameters5/5

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

The schema description coverage is 0%, so the description must compensate. It adds detailed meaning for the single parameter 'script', explaining it as 'Python code to execute in Blender' with access to 'bpy' and 'send_status()', which clarifies semantics not evident from the schema alone.

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 the specific action ('Execute a Python script inside Blender') and resource ('Blender'), distinguishing it from sibling tools like 'get_blender_scene' (which retrieves scene data) and 'image_to_3d_model' (which converts images). It explicitly mentions the verb 'execute' and the target environment 'Blender', avoiding tautology.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool (to run Python scripts in Blender) but does not explicitly mention when not to use it or name alternatives. The 'IMPORTANT RULES' section implies usage by setting prerequisites, but it lacks explicit exclusions or comparisons to sibling 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/MITHRAN-BALACHANDER/Blender-MCP-antigravity'

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