Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

setup_physics

Add or configure rigid body, cloth, or collision physics on a Blender object with mass, friction, restitution, and presets.

Instructions

Configure physics simulations on a scene object: Rigid Body dynamics (Active/Passive, mass, friction, restitution, collision shape), Cloth simulation modifier (presets: SILK, COTTON, LEATHER, pinning vertex group, quality), or Collision body (damping, cloth friction, thickness).

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

Input Schema

NameRequiredDescriptionDefault
massNoRigid body or cloth mass in kilograms (0.01 to 10000.0).
actionNoAction to perform (add, remove, configure).add
dampingNoCollision damping factor (0.0 to 1.0).
qualityNoCloth simulation quality steps per frame (1 to 20).
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
frictionNoSurface friction coefficient (0.0 to 1.0 for rigid bodies; 0.0 to 80.0 for cloth collision).
kinematicNoWhether the rigid body is animated / kinematic (driven by animation/script rather than physics forces).
object_nameYesName of the target object to attach or configure physics on.
restitutionNoBounciness / restitution coefficient (0.0 to 1.0).
cloth_presetNoOptional physical cloth preset setting stiffness, shear, and density parameters.
distance_minNoMinimum distance between cloth and external collision objects in meters (0.001 to 1.0).
physics_typeNoPhysics system type.RIGID_BODY
use_breakingNoAllow the constraint to break when impulse exceeds breaking_threshold.
use_pressureNoEnable or disable uniform cloth internal gas pressure simulation.
self_frictionNoFriction coefficient for cloth self-collision (0.0 to 80.0).
target_volumeNoTarget volume factor when use_pressure_volume is enabled (0.0 to 10000.0).
use_collisionNoEnable or disable cloth object collision with other collision objects.
cloth_frictionNoCollision surface friction against cloth (0.0 to 80.0).
linear_dampingNoAmount of linear velocity lost over time for rigid body (0.0 to 1.0).
angular_dampingNoAmount of angular velocity lost over time for rigid body (0.0 to 1.0).
collision_shapeNoRigid body collision boundary shape.CONVEX_HULL
constraint_typeNoRigid body constraint type (FIXED, POINT, HINGE, SLIDER, GENERIC).FIXED
pressure_factorNoPressure scaling factor (0.0 to 10000.0).
rigid_body_typeNoRigid body simulation type (ACTIVE or PASSIVE).ACTIVE
target_object_1NoFirst object connected by the rigid body constraint (defaults to object_name if omitted).
target_object_2NoSecond object connected by the rigid body constraint (optional; connects to world if omitted).
thickness_outerNoOuter collision distance around mesh surface (0.001 to 1.0).
use_limit_ang_xNoEnable angular rotation limit around the X axis.
use_limit_ang_yNoEnable angular rotation limit around the Y axis.
use_limit_ang_zNoEnable angular rotation limit around the Z axis.
use_limit_lin_xNoEnable linear translation limit along the X axis.
use_limit_lin_yNoEnable linear translation limit along the Y axis.
use_limit_lin_zNoEnable linear translation limit along the Z axis.
pin_vertex_groupNoOptional vertex group name used for mass pinning in cloth simulation.
collision_qualityNoCollision quality steps for cloth collision solver (1 to 20).
limit_ang_x_lowerNoLower angular rotation limit around the X axis in radians (-100.0 to 100.0).
limit_ang_x_upperNoUpper angular rotation limit around the X axis in radians (-100.0 to 100.0).
limit_ang_y_lowerNoLower angular rotation limit around the Y axis in radians (-100.0 to 100.0).
limit_ang_y_upperNoUpper angular rotation limit around the Y axis in radians (-100.0 to 100.0).
limit_ang_z_lowerNoLower angular rotation limit around the Z axis in radians (-100.0 to 100.0).
limit_ang_z_upperNoUpper angular rotation limit around the Z axis in radians (-100.0 to 100.0).
limit_lin_x_lowerNoLower linear translation limit along the X axis in meters (-10000.0 to 10000.0).
limit_lin_x_upperNoUpper linear translation limit along the X axis in meters (-10000.0 to 10000.0).
limit_lin_y_lowerNoLower linear translation limit along the Y axis in meters (-10000.0 to 10000.0).
limit_lin_y_upperNoUpper linear translation limit along the Y axis in meters (-10000.0 to 10000.0).
limit_lin_z_lowerNoLower linear translation limit along the Z axis in meters (-10000.0 to 10000.0).
limit_lin_z_upperNoUpper linear translation limit along the Z axis in meters (-10000.0 to 10000.0).
self_distance_minNoMinimum distance between colliding cloth faces/vertices in meters (0.0005 to 0.1).
breaking_thresholdNoThreshold of linear/angular impulse required to break the constraint (0.0 to 100000.0).
disable_collisionsNoDisable collisions between the two constrained objects.
use_self_collisionNoEnable or disable cloth self-collision.
use_pressure_volumeNoAuto-adjust pressure to preserve or target a specific volume.
expected_snapshot_idNoExpected state snapshot ID for optimistic concurrency control.
use_internal_springsNoEnable or disable cloth internal spring generation across 3D mesh volume.
uniform_pressure_forceNoUniform pressure force applied outwards in Pascals (-10000.0 to 10000.0; positive inflates, negative deflates).
internal_spring_max_lengthNoMaximum length of internal springs in meters (0.0 means unconstrained / no limit; 0.0 to 1000.0).
internal_tension_stiffnessNoTension stiffness of internal springs (0.0 to 10000.0).
internal_spring_normal_checkNoCheck that internal springs align with face normals to avoid inverted springs.
internal_compression_stiffnessNoCompression stiffness of internal springs (0.0 to 10000.0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It names configurable physics categories but does not disclose mutation side effects, permission requirements, reversibility, or what the add/remove/configure actions do to existing settings.

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 a single front-loaded sentence with no wasted words. It is dense because it packs three physics categories into parenthetical lists, but it remains readable and appropriately concise.

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 60-parameter mutation tool with no annotations and no output schema, the description is too high-level. It omits action semantics, the required object_name parameter, side effects, and other behavioral details an agent needs before invoking it.

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 description coverage is 100%, so the schema already documents all 60 parameters. The description adds useful grouping by physics type and mentions cloth presets, but it does not add syntax, default, or constraint meaning beyond what the schema provides.

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 description uses a specific verb, "Configure," and resource, "physics simulations on a scene object," and enumerates three supported physics categories. It is clear what the tool does, but it does not differentiate itself from sibling tools such as configure_physics or manage_physics.

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?

The description implies usage by saying it configures physics simulations, but it gives no explicit when-to-use guidance, no when-not-to-use guidance, and no alternatives. An agent must infer the selection criteria from the tool name alone.

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