Skip to main content
Glama
Sign In
blender-mcp-bridge

blender-mcp-bridge

by otinori
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

blender/execute_python

Run arbitrary Python code within Blender and capture output in the 'result' variable.

Instructions

任意の Python コードを Blender 内で実行する（上級者向け）

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": "blender/execute_python"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes実行する Python コード（result 変数に dict を格納して返す）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description wholly bears the burden of behavioral disclosure. It fails to warn about potential side effects, resource consumption, security risks, or error handling of arbitrary code execution.

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?

A single, front-loaded sentence with parenthetical clarification. Every element is meaningful and the description is appropriately concise.

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?

For a powerful arbitrary code execution tool, the description omits critical context such as security implications, required permissions, side effects on the Blender scene, and the expected format of the result. The presence of sibling tools for specific operations underscores the need for clearer boundaries.

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 coverage is 100% and the parameter description already explains the 'result' variable. The tool description does not add additional semantic value beyond what the schema provides.

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 tool executes arbitrary Python code in Blender, and the parenthetical '(for advanced users)' distinguishes it from the specific operations of sibling tools.

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?

No guidance is provided on when to use this tool versus the specific sibling tools (e.g., for unsupported operations). The mention 'for advanced users' implies caution but is insufficient as explicit usage guidance.

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