Skip to main content
Glama

reset_transform

Reset an object's location, rotation, and scale channels by name to restore its default transform in Blender.

Instructions

Reset object transform channels.

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": "reset_transform"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
scaleNo
locationNo
rotationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry behavioral context. "Reset" implies a mutation that changes object state, but the description does not disclose whether it resets to defaults, whether it is undoable, what selection or permissions it requires, or what happens to channels not reset.

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 single sentence is front-loaded and free of filler, leading directly with the action. Its structure is clean, though the extreme brevity leaves the definition under-explained elsewhere.

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 four-parameter mutation tool with no annotations and an output schema, the definition is under-specified: it omits selection preconditions, toggle semantics, and side-effect disclosure. The output schema helps with return values but not with invocation.

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% for four parameters. The word "channels" hints at location/rotation/scale, but the description does not explain the name parameter, the boolean toggles, or the default=true behavior.

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?

The definition pairs a specific verb ("Reset") with a specific resource ("object transform channels"), so an agent can tell it resets transforms rather than setting or applying them. It does not explicitly differentiate from sibling operations, so it is not 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 statement of when to choose this over set_object_transform or apply_transform, nor any prerequisites such as required object selection. The only implied use is resetting transform channels.

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