Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

calibrate_reference_views

Align, scale, and position multi-view reference planes around a shared origin or target bounding box for consistent scale, ground alignment, and orthogonal placement in reference-driven modeling.

Instructions

Align, scale, and position multi-view reference planes (FRONT, SIDE, TOP) in 3D space around a shared origin or target bounding box. Ensures consistent scale, ground alignment, and orthogonal placement for reference-driven modeling.

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": {
      "views": "<views>"
    },
    "name": "calibrate_reference_views"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewsYesList of reference views to calibrate.
originNo3D spatial origin [x, y, z] in Blender units (meters) around which views are centered.
align_groundNoIf true, aligns bottom of Front and Side reference planes to ground level (Z = origin_z or min_z).
reorient_rotationsNoIf true, enforces canonical orthographic Euler rotations for each view axis.
target_bounding_boxNoTarget model world-space bounding box [min_x, min_y, min_z, max_x, max_y, max_z] in meters. Must be non-degenerate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does reveal that planes get scaled, ground-aligned, and orthogonally reoriented, but those behaviors are already spelled out in the schema field descriptions, and the description omits what happens to existing transforms, whether the operation is idempotent, and what errors occur when a named object is missing.

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, both dense and front-loaded with the verb and resource before the rationale. No filler or repetition, though the second sentence is largely a restatement of behaviors already enumerated in the schema.

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 five-parameter scene-mutating tool with no annotations and no output schema, the description leaves notable gaps: it does not state what is returned (e.g., transform results or success confirmation), what happens to pre-existing plane placement, or how conflicts between origin and target_bounding_box are resolved. It is adequate given the rich schema but not complete on its own.

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%, so every parameter is already documented at field level. The description only reinforces the two anchor modes (origin vs. target_bounding_box) without adding format, constraint, or precedence details beyond the schema, which matches the baseline of 3.

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 opens with a concrete verb set (align, scale, position) applied to a specific resource (multi-view reference planes FRONT/SIDE/TOP) and names the spatial anchors (shared origin or target bounding box). The operation is clearly distinguishable from sibling tools like crop_reference_image or load_reference_image, though no sibling is named 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 context is only implied through the phrase 'for reference-driven modeling,' which suggests the setup stage but gives no explicit when-to-call trigger. There is no guidance on prerequisites (reference objects must already exist in the scene) or on when to prefer this over manual per-object transforms.

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