Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

transform_object

Transform an existing Blender object by setting or offsetting its location, rotation, and scale, with absolute or relative modes; requires trusted approval for scene changes.

Instructions

Transform an existing object in the active Blender scene by setting or offsetting its location, rotation (Euler in radians), and/or scale. Requires explicit user approval through a trusted approval mechanism to authorize scene modification. Client- or model-supplied approval flags in tool arguments are untrusted and cannot authorize mutations. Supports absolute transform assignment (default) or relative offset accumulation ('relative': True).

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact name of the existing object in the scene to transform.
scaleNo3D scale factors [sx, sy, sz]. Must be positive numbers (>= 0.0001). When relative=False, sets absolute scale; when relative=True, multiplies current scale.
task_idNoOptional task or workflow identifier for grouping related scene mutation operations.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent. Mutations must be approved through a trusted approval mechanism.
locationNo3D coordinates [x, y, z] in Blender units. When relative=False, sets absolute location; when relative=True, adds translation delta.
relativeNoIf True, transforms are applied relative to current object state (location += loc, rotation += rot, scale *= scale). Defaults to False (absolute assignment).
bone_nameNoOptional pose bone name if transforming an armature bone in pose mode.
rotation_eulerNo3D Euler rotation angles [rx, ry, rz] in radians. When relative=False, sets absolute rotation; when relative=True, adds angular delta.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does well on the highest-risk aspect: it discloses the mandatory trusted approval mechanism and that client-supplied 'approved' flags are untrusted. It omits what happens on failure (object missing, permission denied), whether the operation is undoable, and any return/confirmation behavior.

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?

Three dense sentences with the action and scope front-loaded. The authorization point spans two sentences that could be merged, but the content is non-redundant and no filler is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation tool with no annotations and no output schema, the definition covers authorization, mode selection, and target scope adequately. The remaining gap is error/return behavior, which is more than its absence of an output schema would excuse.

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 the schema already documents units, bounds, and relative/absolute behavior for each field. The description restates 'Euler in radians' and the absolute-vs-relative semantics rather than adding new meaning such as ordering, validation, or conflict rules between parameters.

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 ('Transform an existing object in the active Blender scene') plus the exact attributes touched (location, rotation, scale). This implicitly separates it from transform_vse_strip (objects, not strips) and from read-only siblings, 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?

Gives clear capability guidance on the two modes (absolute assignment by default vs. 'relative': True for offset accumulation) and states the approval precondition. It does not say when to prefer this over adjacent tools like align_object_grid or duplicate_object, leaving alternative selection to inference.

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