Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_origin

Set the origin point of a Blender object to geometry, 3D cursor, center of mass, or center of volume. Defaults to geometry.

Instructions

Set the origin point of an object.

Args: object_name: Name of the object. type: Origin type. One of: GEOMETRY (origin to geometry center), CURSOR (origin to 3D cursor), CENTER_OF_MASS (origin to center of mass), CENTER_OF_VOLUME (origin to center of volume). Defaults to GEOMETRY.

Returns: Confirmation dict with new origin location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoGEOMETRY
object_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / type / default
      Previous value: -"ORIGIN_GEOMETRY"New value: +"GEOMETRY"
    • addedInput schema / properties / type / enum
      Added value: +[
+  "CENTER_OF_MASS",
+  "CENTER_OF_VOLUME",
+  "CURSOR",
+  "GEOMETRY"
+]
  2. Changed4 schema fields changedv1.2.2
    • removedInput schema / properties / name
      Removed value: -{
-  "title": "Name",
-  "type": "string"
-}
    • addedInput schema / properties / object_name
      Added value: +{
+  "title": "Object Name",
+  "type": "string"
+}
    • changedInput schema / properties / type / default
      Previous value: -"GEOMETRY"New value: +"ORIGIN_GEOMETRY"
    • changedInput schema / required
      Previous value: -[
-  "name"
-]New value: +[
+  "object_name"
+]
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the return value but does not describe side effects, required object state, whether geometry is affected, or any permission or mode requirements.

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 well structured with Args and Returns sections. The Returns section is somewhat redundant because an output schema exists, but it remains concise and useful.

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 simple two-parameter tool with an output schema, the description covers parameters and return value adequately. However, with no annotations, it leaves important behavioral and usage context unspecified, making it only minimally complete.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description defines both parameters clearly. It explains object_name and gives detailed enum semantics for type, including the default of GEOMETRY, which significantly compensates for the missing schema descriptions.

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 uses a specific verb and resource: 'Set the origin point of an object.' This clearly differentiates it from sibling transform tools such as set_location, set_rotation, and set_scale. No ambiguity remains about what the tool does.

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 does not state when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. It only explains the origin type options, which is parameter guidance rather than tool-selection guidance.

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