Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

set_object_origin

Repositions an object's local origin or pivot while preserving world-space vertex coordinates, with modes for bottom center, center of mass, cursor, and custom points.

Instructions

Reposition an object's local origin/pivot point while preserving world-space vertex coordinates. Supports 'BOTTOM_CENTER', 'CENTER_OF_MASS', 'ORIGIN_TO_GEOMETRY', 'GEOMETRY_TO_ORIGIN', 'ORIGIN_TO_CURSOR', 'CUSTOM_POINT'.

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": {
      "object_name": "<object_name>"
    },
    "name": "set_object_origin"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNo
approvedNo
request_idNo
object_nameYesName of the target mesh object.
origin_modeNoTarget origin placement mode.BOTTOM_CENTER
custom_pointNoWorld [x, y, z] point when origin_mode is 'CUSTOM_POINT'.
approval_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses that world-space vertex coordinates are preserved, but it does not explain approval handling, side effects, whether the mesh is modified destructively, or how task_id, approved, request_id, and approval_token affect execution.

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?

The description is front-loaded and compact, with the key behavior stated first. The second sentence duplicates the enum values already exposed in the schema, so it is slightly redundant but still efficient overall.

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?

This is a mutation tool with seven parameters, no annotations, and no output schema, so the description must carry more explanatory weight. It omits the approval workflow and parameter semantics, leaving an agent without enough information to invoke the tool safely beyond the basic purpose.

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

Parameters2/5

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

Schema description coverage is only 43%, so the description should compensate for undocumented parameters. Instead it only repeats the origin_mode enum values already present in the schema and adds no meaning for task_id, request_id, approved, approval_token, or the conditional use of custom_point.

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 states a specific verb and resource: repositioning an object's local origin/pivot point. It also distinguishes the operation by noting that world-space vertex coordinates are preserved, which separates it from generic transform 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?

The description says what the tool does but gives no explicit guidance on when to use it versus alternatives such as transform_object or align_object_grid. The list of supported origin modes is capability information, not usage guidance or exclusions.

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