Skip to main content
Glama

apply_transform

Bakes an object's location, rotation, and scale into its mesh data in Blender, allowing transforms to be reset without changing the object's position.

Instructions

Apply object transform.

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": "apply_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

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 behavioral burden, yet it says nothing about whether this mutates object data, bakes transforms into geometry, resets transform values, or is reversible. The mutation implications of "apply" are left entirely unexplained.

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 sentence is short, but it is under-specified rather than concise. It is front-loaded with a near-tautology and contains no useful detail that would earn its place.

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?

For a four-parameter mutation tool with no annotations, no schema descriptions, and multiple ambiguous siblings, the definition is far too thin. The existence of an output schema removes the need to document return values, but the input and behavioral semantics remain almost entirely undocumented.

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%, and the description gives no information about the four parameters. It does not explain what the required name refers to or what the scale, location, and rotation booleans control, so the agent must infer everything from bare parameter names and defaults.

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?

"Apply object transform" essentially restates the tool name and adds no clarifying scope. It does not distinguish the operation from sibling tools such as set_object_transform, reset_transform, or get_object_transform, so an agent cannot tell what "apply" actually means here.

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?

The description provides no when-to-use guidance, no exclusions, and no mention of alternatives. With siblings like set_object_transform and reset_transform present, the lack of routing guidance is a serious omission.

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