Skip to main content
Glama

move_object

Reposition a named object to specified coordinates in world or custom space, enabling precise scene layout and animation setup in Blender.

Instructions

Move an object.

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>",
      "location": "<location>"
    },
    "name": "move_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
spaceNoworld
locationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden and discloses nothing. It does not state whether coordinates are world- or local-space, whether the move is absolute or relative, whether child objects follow, 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.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded but conveys no information beyond the tool name — this is under-specification masquerading as brevity, not economical writing.

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

Completeness1/5

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

An output schema exists, so return values need not be described, but for a mutation tool with three undocumented parameters and zero annotations the description is essentially empty. Nothing an agent needs in order to call it correctly is present.

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

Parameters1/5

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

Schema description coverage is 0% across three parameters, and the description compensates for none of it. The critical ambiguity of "location" (world vs. local frame, and its interaction with the "space" parameter defaulting to "world") is entirely unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Move an object" restates the tool name and title with no additional specificity. It does not distinguish the tool from move_object_to_collection, and it never says whether "move" means setting an absolute transform, applying a delta, or repositioning in the scene graph.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 preconditions (object must exist, must be selected?), and no mention of how it differs from move_object_to_collection or set_object_transform. An agent must guess which sibling performs a reposition.

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