Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_fluid_simulation

Create, configure, inspect, or remove Mantaflow gas, smoke, and liquid simulations in Blender with domains, flows, effectors, validated parameters, and rollback safeguards.

Instructions

Create, configure, inspect, or remove Mantaflow fluid simulations (Domain, Flow, Effector) for gas/smoke volumetrics and liquid simulations with parameter validation, safe interactive limits, optimistic concurrency, and transactional rollback.

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

Input Schema

NameRequiredDescriptionDefault
betaNoGas buoyancy heat factor (-5.0 to 5.0). Defaults to 1.0.
nameNoAlias for object_name.
alphaNoGas buoyancy density factor (-5.0 to 5.0). Defaults to 1.0.
actionNoAction to perform: 'create'/'add', 'configure', 'inspect', or 'remove'/'delete'. Defaults to 'create'.create
densityNoFlow emission density (0.0 to 10.0). Defaults to 1.0.
task_idNoOptional task identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
use_meshNoWhether surface mesh generation is enabled for liquid domain. Defaults to True.
flow_typeNoFlow emission type: 'SMOKE', 'BOTH' (fire+smoke), 'FIRE', or 'LIQUID'. Defaults to 'SMOKE'.SMOKE
subframesNoEmission subframes for fast-moving flow/effector objects (0 to 200). Defaults to 0.
vorticityNoGas turbulence vorticity / swirl factor (0.0 to 4.0). Defaults to 0.0.
cache_typeNoCache type for domain ('REPLAY', 'MODULAR', 'ALL'). Defaults to 'REPLAY'.REPLAY
flip_ratioNoRatio of FLIP to PIC velocity update (0.0 to 1.0). Defaults to 0.97.
fluid_typeNoFluid role on object: 'DOMAIN' (gas/liquid boundary), 'FLOW' (emitter/inflow/outflow), or 'EFFECTOR' (collision/guide). Defaults to 'DOMAIN'.DOMAIN
mesh_scaleNoResolution scale factor for generated liquid mesh (1 to 100). Defaults to 2.
time_scaleNoSimulation time playback scale (0.0001 to 10.0). Defaults to 1.0.
use_inflowNoWhether inflow is actively emitting. Defaults to True.
domain_typeNoDomain simulation type: 'GAS' (smoke/fire volumetrics) or 'LIQUID' (water/fluid surface). Defaults to 'GAS'.GAS
flame_smokeNoAmount of smoke generated by fire (0.0 to 8.0). Defaults to 1.0.
fuel_amountNoFlow emission fuel amount for fire (0.0 to 10.0). Defaults to 1.0.
object_nameNoName of the target mesh object (alias: name).
snapshot_idNoAlias for expected_snapshot_id.
temperatureNoFlow emission temperature difference (-10.0 to 10.0). Defaults to 1.0.
burning_rateNoFire burning speed rate (0.01 to 4.0). Defaults to 0.75.
use_effectorNoWhether effector influence is enabled. Defaults to True.
cfl_conditionNoCFL condition threshold (0.0 to 10.0). Defaults to 2.0.
effector_typeNoEffector role: 'COLLISION' (solid obstacle/deflector) or 'GUIDE' (flow director). Defaults to 'COLLISION'.COLLISION
flow_behaviorNoFlow behavior: 'INFLOW' (continuous stream), 'OUTFLOW' (drain/sink), or 'GEOMETRY' (one-time volume). Defaults to 'GEOMETRY'.GEOMETRY
timesteps_maxNoMaximum simulation timesteps per frame (1 to 100). Defaults to 4.
timesteps_minNoMinimum simulation timesteps per frame (1 to 100). Defaults to 1.
use_diffusionNoWhether liquid viscosity diffusion is enabled. Defaults to False.
dissolve_speedNoNumber of frames for smoke to dissolve (1 to 10000). Defaults to 5.
resolution_maxNoMax resolution divisions for fluid domain grid (16 to 256). Defaults to 32.
use_plane_initNoTreat effector as planar surface rather than closed volume. Defaults to False.
velocity_coordNoCartesian initial velocity vector [X, Y, Z]. Defaults to [0.0, 0.0, 0.0].
viscosity_baseNoViscosity base factor for liquid (0.0 to 10.0). Defaults to 1.0.
cache_frame_endNoEnd frame of simulation cache (1 to 100000, max span <= 250). Defaults to 50.
flame_vorticityNoAdditional vorticity created by flames (0.0 to 2.0). Defaults to 0.5.
particle_radiusNoParticle radius factor relative to cell size (0.0 to 10.0). Defaults to 1.0.
surface_tensionNoSurface tension of liquid (0.0 to 100.0). Defaults to 0.0.
velocity_factorNoVelocity multiplier (-100.0 to 100.0). Defaults to 1.0.
velocity_normalNoNormal velocity component (-100.0 to 100.0). Defaults to 0.0.
surface_distanceNoDistance from mesh surface for flow/effector emission (0.0 to 10.0). Defaults to 1.0 for flow, 0.0 for effector.
cache_frame_startNoStart frame of simulation cache (1 to 100000). Defaults to 1.
simulation_methodNoLiquid simulation method ('FLIP' or 'APIC'). Defaults to 'FLIP'.FLIP
use_dissolve_smokeNoWhether smoke dissolves over time. Defaults to False.
viscosity_exponentNoViscosity exponent value (10^-n) (0 to 10). Defaults to 6.
expected_snapshot_idNoExpected state snapshot ID for optimistic concurrency control.
use_initial_velocityNoWhether to impart initial velocity to emitted fluid. Defaults to False.
use_adaptive_timestepsNoWhether to use adaptive timestepping based on CFL condition. Defaults to True.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/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 usefully discloses parameter validation, safe interactive limits, optimistic concurrency, and transactional rollback, but it does not explain destructive semantics for remove, permission requirements, or what happens to existing simulation data during create/configure.

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 definition is a single front-loaded sentence that states the main verbs and resource before adding behavioral traits. It is efficient, though the long list of safeguards makes it slightly dense.

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?

Given the high complexity of a 50-parameter, multi-action tool with no annotations and no output schema, the description provides useful high-level behavioral context. However, it does not clarify action-specific requirements, removal consequences, or concurrency behavior in enough detail for an agent to fully understand the tool's operational boundaries.

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 input schema already documents all 50 parameters in detail. The description adds conceptual grouping around Domain, Flow, and Effector but does not add syntax, constraints, or action-specific parameter meaning beyond the schema.

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 names concrete verbs (create, configure, inspect, remove) and the resource (Mantaflow fluid simulations with Domain, Flow, Effector roles), so the tool's broad purpose is clear. It does not distinguish itself from the sibling inspect_fluid_simulation tool, and the inclusion of an inspect action creates ambiguity about which tool should be used for inspection.

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 lists possible actions but gives no explicit guidance on when to use this tool versus alternatives such as inspect_fluid_simulation or bake_physics_simulation. It also does not explain when to choose create versus configure versus remove, leaving action selection to the schema 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