Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_force_field

Create, configure, inspect, or remove WIND, TURBULENCE, and VORTEX physics force fields with parameter controls and transactional rollback in Blender.

Instructions

Create, configure, inspect, or remove physics force fields (WIND, TURBULENCE, VORTEX) with full parameter controls (strength, flow, wind_factor, size, inflow, noise, seed, falloff, limits) 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_force_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowNoAir flow velocity conversion factor (0.0 to 1000.0). Defaults to 0.0.
nameNoName of the force field object to create, configure, inspect, or remove (alias: object_name).
seedNoRandom seed for force field noise evaluation (1 to 128). Defaults to 1.
sizeNoSize scale of the turbulence perturbation (0.0 to 1000.0, for TURBULENCE). Defaults to 1.0.
noiseNoAmount of noise perturbation added to force strength (0.0 to 10.0). Defaults to 0.0.
shapeNoDirectional effector shape calculation. Defaults to POINT.POINT
actionNoAction to perform: 'create'/'add', 'configure', 'inspect', or 'remove'/'delete'. Defaults to 'create'.create
inflowNoInwards radial suction component of vortex force (-1000.0 to 1000.0, for VORTEX). Defaults to 0.0.
task_idNoOptional task identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
locationNoWorld coordinate location [x, y, z] for new or transformed force field.
rotationNoEuler rotation [rx, ry, rz] in radians (defines orientation for directional fields like WIND).
strengthNoStrength of the force field (-100000.0 to 100000.0). Defaults to 1.0.
field_typeNoForce field type: WIND (directional air velocity), TURBULENCE (pseudorandom turbulent disturbance), or VORTEX (spiral vortex flow).WIND
object_nameNoAlias for name.
snapshot_idNoAlias for expected_snapshot_id.
wind_factorNoHow much the force is reduced when acting parallel to a surface (0.0 to 1.0, e.g. cloth). Defaults to 1.0.
z_directionNoEffect in full, positive, or negative Z direction. Defaults to BOTH.BOTH
distance_maxNoMaximum distance for field influence (0.0 to 100000.0). Defaults to 0.0.
distance_minNoMinimum distance for field falloff (0.0 to 1000.0). Defaults to 0.0.
falloff_typeNoFalloff geometry shape. Defaults to SPHERE.SPHERE
use_2d_forceNoApply force only in the 2D plane perpendicular to local Z. Defaults to False.
delete_objectNoFor remove action: whether to delete the empty object itself (True) or only reset field type to NONE (False). Defaults to False.
falloff_powerNoPower of distance falloff curve (0.0 to 10.0). Defaults to 0.0.
use_max_distanceNoWhether to enforce a maximum distance for force influence. Defaults to False.
use_min_distanceNoWhether to enforce a minimum distance for force falloff. Defaults to False.
use_global_coordsNoUse effector global coordinates for turbulence noise evaluation (for TURBULENCE). Defaults to False.
expected_snapshot_idNoExpected state snapshot ID for optimistic concurrency control.

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 supplied, so the description carries the full burden. It does disclose one genuinely useful trait not found in structured fields — 'transactional rollback' — but says nothing about permissions, whether 'configure' overwrites unspecified parameters, or what 'remove' returns. For a 28-parameter mutation tool with zero annotation coverage, that is thin.

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?

A single dense, front-loaded sentence that states operations first, resource second, controls third. Nothing is padding, though the parenthetical parameter list is close to restating the schema and could be trimmed.

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 28-parameter tool with no annotations and no output schema, the description covers purpose and atomicity but omits what 'inspect' returns, how missing parameters are treated on 'configure', and any safety expectations around 'remove'. It is workable because the schema is fully documented, but not complete.

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% with ranges, enums and defaults for every parameter, so the baseline is 3. The description merely re-lists parameter names (strength, flow, wind_factor, size, inflow, noise, seed, falloff, limits) without adding semantics such as which parameters apply only to VORTEX or TURBULENCE.

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 a concrete resource (physics force fields) with the three concrete types (WIND, TURBULENCE, VORTEX) and the four operations it covers (create, configure, inspect, remove), so an agent can tell it apart from configure_physics or configure_fluid_simulation. It loses a point because it claims 'inspect' while a dedicated inspect_force_field sibling exists, blurring which tool an agent should pick for reads.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives such as inspect_force_field or configure_physics. The enumerated actions mirror the schema's action enum, so the sentence adds essentially no routing guidance beyond structured data.

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