Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_particle_system

Create, configure, inspect, or remove emitter and hair particle systems on Blender mesh objects, including count, lifetime, velocity, hair dynamics, and instancing, with rollback support.

Instructions

Create, configure, inspect, or remove emitter or hair particle systems on mesh objects with full parameter controls (count, lifetime, initial velocity, hair dynamics cloth solver, object/collection instancing) 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_particle_system"
  }
}

Input Schema

NameRequiredDescriptionDefault
massNoMass of individual particles in kg (0.00001 to 10000.0). Defaults to 1.0.
nameNoAlias for object_name.
countNoTotal number of emitted particles (1 to 1000000). Defaults to 1000.
actionNoAction to perform: 'create'/'add', 'configure', 'inspect', or 'remove'/'delete'. Defaults to 'create'.create
task_idNoOptional task identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
lifetimeNoLifetime of particles in frames (0.1 to 100000.0). Defaults to 50.0.
frame_endNoEnding frame for particle emission. Defaults to 200.0.
hair_stepNoNumber of hair segments/keys per strand (1 to 7). Used when system_type is HAIR. Defaults to 5.
frame_startNoStarting frame for particle emission. Defaults to 1.0.
hair_lengthNoLength of hair strands in meters (0.0001 to 10000.0). Used when system_type is HAIR. Defaults to 4.0.
object_nameNoName of the target mesh object (alias: name).
render_typeNoParticle visualization/instancing render type. Defaults to HALO.HALO
size_randomNoRandom size variation factor (0.0 to 1.0). Defaults to 0.0.
snapshot_idNoAlias for expected_snapshot_id.
system_nameNoName of the particle system (default: 'ParticleSystem').ParticleSystem
system_typeNoParticle system type ('EMITTER' or 'HAIR'). Defaults to 'EMITTER'.EMITTER
physics_typeNoParticle physics solver type. Defaults to NEWTON.NEWTON
factor_randomNoRandom velocity perturbation factor (0.0 to 1000.0). Defaults to 0.0.
normal_factorNoInitial velocity along surface normal (-1000.0 to 1000.0). Defaults to 1.0.
object_factorNoEmitter object movement velocity factor (0.0 to 1000.0). Defaults to 0.0.
particle_sizeNoDisplay/instance size of particles in meters (0.0001 to 1000.0). Defaults to 0.05.
tangent_factorNoInitial velocity along surface tangent (-1000.0 to 1000.0). Defaults to 0.0.
delete_settingsNoOn removal: whether to delete unlinked ParticleSettings datablock from blender data. Defaults to True.
instance_objectNoName of object to instance for each particle (used when render_type is OBJECT).
lifetime_randomNoRandom variation factor for particle lifetime (0.0 to 1.0). Defaults to 0.0.
use_hair_dynamicsNoWhether physics dynamics (cloth solver) is enabled for hair strands. Defaults to False.
hair_dynamics_massNoHair dynamics mass per strand in kg (0.0001 to 10000.0). Defaults to 1.0.
use_scale_instanceNoWhether instanced object/collection scales with particle size. Defaults to True.
instance_collectionNoName of collection to instance for particles (used when render_type is COLLECTION).
object_align_factorNoInitial velocity aligned with object axes [x, y, z].
use_global_instanceNoWhether to use global coordinates for instanced object. Defaults to False.
expected_snapshot_idNoExpected state snapshot ID for optimistic concurrency control.
hair_dynamics_qualityNoHair dynamics simulation solver quality steps (1 to 80). Defaults to 5.
hair_dynamics_air_dampingNoHair dynamics air damping (0.0 to 10.0). Defaults to 1.0.
hair_dynamics_pin_stiffnessNoHair dynamics pin stiffness at the root (0.0 to 10000.0). Defaults to 1.0.
hair_dynamics_bending_stiffnessNoHair dynamics bending stiffness (0.0 to 10000.0). Defaults to 0.5.

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 valuable trait beyond the schema: 'transactional rollback' implies atomic failure semantics, and 'remove' flags a destructive action. However, it omits what removal destroys (delete_settings drops the ParticleSettings datablock), how snapshot conflicts are surfaced, and what the tool returns after a create vs. an inspect.

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 front-loaded sentence with the verbs first and the scope qualifiers after; the parenthetical is dense but informative rather than padded. Slightly overloaded but no wasted clauses.

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 37-parameter, six-action tool with no annotations and no output schema, the definition is thin: it doesn't say which parameters matter for which action (create vs. configure vs. remove) or what a successful inspect returns. The complete schema descriptions compensate substantially, keeping this at a minimum-viable level rather than inadequate.

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 the baseline is 3. The parenthetical (count, lifetime, initial velocity, hair dynamics, instancing) usefully groups the 37 parameters into families, but adds no constraints, defaults, or action-specific applicability beyond what the schema already states per field.

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 specific verbs (create, configure, inspect, remove), the resource (emitter or hair particle systems), and the target (mesh objects), plus the parameter families covered. It is easy to separate from siblings like configure_physics or configure_force_field, though the overlap with the sibling inspect_particle_system is not addressed.

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 explicit when-to-use or when-not guidance; the multi-action enum (create/configure/inspect/remove) implies dispatch but the description never says when an agent should call this instead of inspect_particle_system or other configure_* tools. Usage must be inferred from the action names 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