Skip to main content
Glama

rotate_object

Rotate a Blender object by specifying its name and Euler rotation in radians. Use it to orient 3D models precisely within your scene.

Instructions

Rotate an object (Euler radians).

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>",
      "rotation": "<rotation>"
    },
    "name": "rotate_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
spaceNoworld
rotationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are supplied, so the description carries the full behavioral burden and largely fails. It does not state whether the rotation is absolute or additive to the current orientation, whether it operates in world or local space by default, what happens to objects with existing animation, or whether the operation is undoable.

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?

A single short sentence with the key unit information front-loaded and zero padding. It is efficient, though the extreme brevity reflects under-specification rather than disciplined editing.

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?

For a mutation tool with no annotations, 0% parameter description coverage, and a meaningful 'space' parameter left unexplained, the description does far too little. An output schema exists so return values need not be covered, but the core semantics of the rotation and space arguments are missing.

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 0%, so the description must compensate for three undocumented parameters. 'Euler radians' usefully fixes the format and units of the rotation array, but the 'name' target resolution and the 'space' parameter (world vs local, defaulting to world) remain completely undefined.

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 ('Rotate') and resource ('an object'), and the parenthetical clarifies the rotation representation as Euler radians. It is distinguishable from move_object and scale_object by name, but gives no explicit sibling differentiation against transform-setting alternatives like set_object_transform.

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?

There is no when-to-use guidance, no mention of prerequisites, and no reference to alternatives such as set_object_transform or get_object_transform. The agent must infer that this is the rotation-specific mutation tool purely from the name.

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