Skip to main content
Glama

bake_physics

Bakes a Blender object's physics simulation to finalize its motion; specify a physics type or omit it to bake all physics on the object.

Instructions

Bake a physics simulation for an object.

Args: object_name: Name of the object with physics. physics_type: Optional physics type to bake: RIGID_BODY, CLOTH, FLUID, PARTICLE_SYSTEM or SOFT_BODY. If empty, bakes all physics on the object.

Returns: Confirmation dict.

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": {
      "object_name": "<object_name>"
    },
    "name": "bake_physics"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_nameYes
physics_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • changedInput schema / properties / physics_type / enum
      Previous value: -[
      -  "CLOTH",
      -  "FLUID",
      -  "PARTICLE_SYSTEM",
      -  "RIGID_BODY"
      -]New value: +[
      +  "CLOTH",
      +  "FLUID",
      +  "PARTICLE_SYSTEM",
      +  "RIGID_BODY",
      +  "SOFT_BODY"
      +]
  2. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / physics_type / enum
      Added value: +[
      +  "CLOTH",
      +  "FLUID",
      +  "PARTICLE_SYSTEM",
      +  "RIGID_BODY"
      +]
  3. First observedv0.1.0

TDQS

A3.6/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. It explains that leaving physics_type empty bakes all physics on the object, but it does not disclose whether the object must already have physics, whether baking is destructive or reversible, what simulation prerequisites exist, or what the confirmation dict contains.

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 description is front-loaded with the core action, then uses Args and Returns sections efficiently. The enum list is slightly redundant with the schema, but otherwise every sentence contributes useful information.

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 description covers the operation and both parameters adequately, and the output schema exists so detailed return-value documentation is less necessary. However, for a mutation-style operation with no annotations, it lacks enough behavioral context about preconditions, side effects, and failure modes.

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

Parameters4/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. It documents both parameters: object_name as the object with physics, and physics_type as an optional enum with the important default behavior that an empty value bakes all physics.

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

Purpose5/5

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

The description states a specific verb and resource: "Bake a physics simulation for an object." This clearly distinguishes it from sibling tools like add_rigid_body or bake_texture, since the action and domain are both explicit.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the purpose statement: this is the tool for baking existing physics on an object. However, there is no explicit guidance on when to choose this over related siblings such as add_*_sim, set_physics_property, or bake_texture, and no prerequisites or exclusions are stated.

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