Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

load_reference_image

Load a reference image as a Blender Image Empty or textured plane for visual alignment and reference-driven 3D modeling. Align it to front, side, or top orthographic views.

Instructions

Load a reference image into the Blender scene as a native Image Empty object or calibrated textured mesh plane for visual alignment and reference-driven 3D modeling. Supports front, side, and top orthographic alignment.

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": {
      "image_path": "<image_path>"
    },
    "name": "load_reference_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName for the created Blender object.Reference_Image
sizeNoPrimary dimension (meters) of the empty display size or plane dimension.
depthNoDisplay depth relative to geometry: 'DEFAULT', 'FRONT', or 'BACK'.DEFAULT
scaleNoScale factors [sx, sy, sz].
opacityNoDisplay transparency/alpha (0.0 = transparent, 1.0 = opaque).
crop_boxNoOptional normalized crop bounds [u_min, v_min, u_max, v_max] in [0.0, 1.0].
locationNo3D spatial position [x, y, z] in Blender units (meters).
view_axisNoOrthographic view alignment: 'FRONT' (facing -Y), 'SIDE' (facing +X), 'TOP' (facing +Z), or 'USER' (custom rotation).FRONT
image_pathYesFilesystem path to the reference image (.png, .jpg, .jpeg, .webp, .tga, .bmp, .tif, .tiff, .exr).
output_pathNoDestination file path for cropped image when crop_box is provided. Must not overwrite source image.
display_modeNoDisplay representation: 'EMPTY' (Blender Image Empty) or 'PLANE' (calibrated textured mesh plane).EMPTY
rotation_eulerNoExplicit Euler rotation [rx, ry, rz] in radians. Overrides view_axis default when provided.
coordinate_systemNoCoordinate convention: 'UV' (default, [0,0] bottom-left) or 'IMAGE_SPACE' ([0,0] top-left).UV

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only says it creates an empty or plane. It omits whether an existing blend/scene is required, whether repeated calls stack new objects or replace them, whether the created object persists in the saved file, and what happens on an invalid path or on crop output failures.

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?

Two sentences, front-loaded with the action and result; the second sentence adds the orthographic alignment capability. Minor redundancy between 'visual alignment' and 'reference-driven 3D modeling', but nothing is wasted.

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 13-parameter creation tool with no annotations and no output schema, the description is thin on side effects and prerequisites (scene state, object persistence, crop output path handling) even though the schema fully documents inputs. It is enough to call correctly but not enough to predict consequences.

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 100%, with all 13 parameters documented including enums for view_axis, display_mode, depth, and coordinate_system, so the baseline is 3. The description only echoes the front/side/top alignment idea already captured by the view_axis enum and adds no new parameter meaning.

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?

States a specific verb and resource ('Load a reference image into the Blender scene') plus the two concrete outcomes (native Image Empty object or calibrated textured mesh plane) and the modeling purpose. It is clearly distinguishable from crop_reference_image or calibrate_reference_views without opening the schema, though it never names a sibling explicitly.

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?

Usage is only implied via 'for visual alignment and reference-driven 3D modeling' and the orthographic-alignment note. There is no explicit when-to-use/when-not guidance and no routing to crop_reference_image (for cropping) or calibrate_reference_views (for calibration), which are the obvious alternatives.

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