Skip to main content
Glama

get_object_transform

Retrieves an object's location, rotation, and scale in world or local space so you can inspect exact transform values before adjusting or animating it in Blender.

Instructions

Get location/rotation/scale for 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>"
    },
    "name": "get_object_transform"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
spaceNoworld

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and only implies read-only via the verb 'get'. It says nothing about whether the object must exist/be selected, whether values are evaluated at the current frame, or how the coordinate space affects results — all meaningful for a transform query.

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 front-loaded sentence with zero filler. Its brevity is efficient, though it borders on under-specification rather than true conciseness.

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?

The output schema covers the return values, and the tool is simple with only two parameters, which limits the damage. However, the unexplained 'space' parameter and absence of conditions for use leave the definition thinner than a transform-query tool warrants.

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 0%, so the description must compensate, yet it never mentions the 'space' parameter at all — a critical distinction (world vs. local) for transform data. 'name' is self-evident, but half the parameters remain semantically undocumented.

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 ('Get location/rotation/scale for an object'), and the returned transform components make it clearly distinguishable from siblings like set_object_transform or get_object_info. No explicit sibling naming, so it falls short of a 5.

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 steering toward alternatives such as get_object_info for broader object data or apply_transform for mutation. The agent must infer that this is the read counterpart to set_object_transform purely from names.

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