Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

sculpt_organic_anatomy

Sculpts organic anatomy on a named Blender mesh with bounded brushes, topology preservation, silhouette-guided checks, and automatic rollback when constraints fail.

Instructions

Bounded organic sculpting and coarse anatomy refinement on an explicitly named mesh. Supports a verified initial brush set ('GRAB', 'INFLATE', 'SMOOTH', 'CLAY', 'DRAW') with bounded radius, strength, stroke coordinates, max displacement, and iteration limits. Preserves topology by default; requires explicit parameter configuration and limits for dynamic topology. Evaluates candidate deformation against calibrated FRONT, SIDE, and TOP silhouette objectives when provided, and enforces transactional rollback if constraints or regression tolerances are violated.

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": {
      "target_object": "<target_object>"
    },
    "name": "sculpt_organic_anatomy"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoOrthographic view if single reference image is specified: 'FRONT', 'SIDE', or 'TOP'.FRONT
viewsNoOptional calibrated multi-view reference configurations (FRONT, SIDE, TOP) for reference-guided acceptance evaluation.
radiusNoBrush influence radius in Blender units (meters).
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
crop_boxNoOptional normalized crop bounds [u_min, v_min, u_max, v_max] in [0.0, 1.0].
strengthNoSculpt brush strength factor in [0.0, 1.0].
objectiveNoMulti-view silhouette objective function: 'WEIGHTED_IOU', 'MIN_IOU', or 'WEIGHTED_DICE'.WEIGHTED_IOU
brush_typeNoSculpt brush operation: 'GRAB' (translation along stroke vector), 'INFLATE' (normal displacement), 'SMOOTH' (Laplacian relaxation), 'CLAY' (surface build-up along average normal), or 'DRAW' (surface displacement).INFLATE
iterationsNoNumber of bounded sculpting passes/iterations to execute.
camera_nameNoOptional scene camera name to use for evaluation.
object_nameNoAlias for target_object.
stroke_pointsNoArray of 3D spatial points [x, y, z] or 2D screen coordinates representing brush contact path.
target_objectYesName of the target mesh object in the Blender scene to sculpt.
max_face_countNoUpper bound limit on allowed polygon face count for resource protection.
affected_regionNoOptional bounding limits for the affected region (center [x, y, z] and max_radius).
dynamic_topologyNoExplicitly enable dynamic topology mode (requires preserve_topology=false).
max_displacementNoMaximum allowed spatial displacement per vertex in Blender units (meters).
max_vertex_countNoUpper bound limit on allowed vertex count for resource protection.
stroke_directionNoExplicit 3D direction vector [dx, dy, dz] for directional brushes like GRAB.
coordinate_systemNoCoordinate system convention: 'UV' or 'IMAGE_SPACE'.UV
preserve_topologyNoStrictly preserve mesh topology (vertex, edge, face count). Defaults to true.
rollback_on_failureNoIf true, automatically rollback mesh state if objective does not strictly improve or regression tolerance is violated.
reference_image_pathNoOptional single reference image path if 'views' is omitted.
dynamic_topology_detailNoDetail size for dynamic topology remeshing in meters.
min_aggregate_improvementNoMinimum required aggregate objective improvement to accept deformation when views are configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does substantial work: it discloses default topology preservation, the requirement that dynamic topology be explicitly enabled alongside preserve_topology=false, objective-based acceptance gating with regression tolerances, and transactional rollback on violation. Missing are permission requirements and cost/performance characteristics for a 26-parameter operation.

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?

It is a single dense paragraph that front-loads the operation and scope before moving to constraints, with no filler sentences. It is long, but every clause covers a distinct behavioral surface of a complex tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 26-parameter sculpting tool with nested view configs and no output schema, the description covers the critical decision points: topology handling, acceptance evaluation, and rollback semantics. It stops short of describing the returned state or how failures are reported, which is the main residual gap.

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 every parameter, and the description largely restates categories (brush set, radius, strength, stroke coordinates, max displacement, iteration limits) rather than adding syntax or interaction rules. Baseline 3 applies when the schema does the heavy lifting.

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 opens with a specific verb-plus-resource statement: 'Bounded organic sculpting and coarse anatomy refinement on an explicitly named mesh.' That distinguishes it from generic mesh editing, though it never names or contrasts with the sibling 'sculpt_mesh' tool, leaving the agent to infer the boundary.

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?

Context is implied by the constraints described (bounded, coarse refinement, reference-guided acceptance), but there is no explicit statement of when to choose this over 'sculpt_mesh', 'inspect_sculpt_state', or 'compare_silhouette_alignment'. The agent gets subject matter, not routing guidance.

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