Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

bake_physics_simulation

Bakes Rigid Body, Cloth, or all physics caches across a bounded frame range (up to 250 frames) and verifies deterministic point caches.

Instructions

Bake physics simulation caches (Rigid Body, Cloth, or All) across a bounded frame range (maximum 250 frames) with deterministic point cache verification.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bake_physics_simulation"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
frame_endNoEnding frame of simulation cache (<= frame_start + 250).
frame_startNoStarting frame of simulation cache (>= 1).
object_nameNoTarget object name for cloth baking. Optional if physics_type is RIGID_BODY or ALL.
physics_typeNoSimulation domain to bake.RIGID_BODY
timeout_secondsNoMaximum execution duration before timeout guard trips (1.0 to 300.0).
expected_snapshot_idNoExpected state snapshot ID for optimistic concurrency control.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does useful work by disclosing the 250-frame bound and that output is a deterministically verified point cache. It omits key mutation behavior: whether existing caches are overwritten, that baking is long-running/blocking (only hinted at via timeout_seconds in the schema), and that cloth requires a specific target object.

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?

One front-loaded sentence with no filler; the domain options and the frame bound are packed into the first clause. It is arguably too terse for an 8-parameter mutation tool, but nothing is wasted.

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?

For a heavy, annotation-free mutation tool with 8 parameters and no output schema, the definition gives no guidance on result reporting (what the verification outcome looks like), failure modes, or prerequisites. The schema fills most parameter gaps, but execution context is thin.

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

Parameters3/5

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

Schema coverage is 100%, so every parameter already has documentation, including the frame_end <= frame_start + 250 constraint and the deprecated approved flag. The description's 'maximum 250 frames' merely restates the schema and adds no new parameter meaning, so the baseline 3 applies.

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 names a specific verb (bake), a specific resource (physics simulation caches), the domains covered (Rigid Body, Cloth, or All), and the scope constraint (bounded frame range, max 250). An agent can distinguish this from the sibling configure_/inspect_/setup_physics tools without opening any schema.

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 only implied: an agent infers this is the execution step after physics has been configured, but the description never states prerequisites, when to prefer a partial bake over ALL, or what to do if a cache already exists. No alternatives or exclusions are named.

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