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

blender-mcp-bridge

by otinori
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

blender/create_object

Create meshes, lights, cameras, and empties in Blender by specifying object type with optional name and position.

Instructions

メッシュ・ライト・カメラ等を作成する

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": {
      "type": "<type>"
    },
    "name": "blender/create_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesオブジェクトタイプ（CUBE / SPHERE / CYLINDER / CONE / PLANE / TORUS / MONKEY / LIGHT / CAMERA / EMPTY）
nameNoオブジェクト名（任意）
locationNo位置 [x, y, z]（任意、デフォルト [0, 0, 0]）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description must disclose side effects and behavior. Only states 'creates' without mentioning defaults like name or location, nor effects on existing objects or scene state.

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?

Single sentence, concise and front-loaded with the action. Could be improved by including key behavioral details without adding verbosity.

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?

Lacks return value description and context about Blender scene operation. With no output schema and low complexity, the description should at least mention that the created object is added to the active scene.

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 has 100% description coverage, so parameters are documented. The description adds no extra semantic meaning beyond what the schema provides.

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?

Description clearly states the tool creates meshes, lights, cameras, etc., differentiating it from sibling tools like delete or list. However, it could be more explicit about the full range of object types.

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 on when to use this tool versus alternatives or prerequisites. Missing context on when not to use, e.g., if object type is not supported.

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