Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

detail_surface_features

Applies bounded fine-scale anatomical surface detailing—scales, ridges, facets, or veins—to a specified mesh while preserving landmarks and topology, with rollback on failure.

Instructions

Applies controlled, bounded fine-scale anatomical surface detailing (SCALES, RIDGES, FACETS, VEINS) on an explicitly designated target mesh. Preserves existing semantic landmarks, prevents multi-view silhouette regression beyond configured tolerances, and maintains strict topology invariants by default with transactional rollback upon failure.

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>",
      "feature_type": "<feature_type>"
    },
    "name": "detail_surface_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoSigned surface relief depth in meters (positive = outward relief, negative = creased indent).
viewsNoOptional calibrated reference views for silhouette regression monitoring.
spacingNoAlias for feature_scale.
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
strengthNoStrength modulation factor in [0.0, 1.0].
iterationsNoNumber of surface detailing passes.
object_nameNoAlias for target_object.
orientationNo3D directional vector [x, y, z] for directional features (RIDGES, VEINS).
falloff_typeNoSpatial boundary falloff function for regional influence.SMOOTH
feature_typeYesType of anatomical surface detail feature to apply.
use_symmetryNoWhether to enforce bilateral symmetry across symmetry_axis during detailing.
feature_scaleNoScale, wavelength, or cellular spacing of the feature pattern in meters.
region_boundsNoOptional bounding box [xmin, ymin, zmin, xmax, ymax, zmax] to restrict deformation.
region_centerNoOptional center coordinate [x, y, z] of the influence region.
region_radiusNoRadius of influence sphere in meters. 0.0 applies to the entire mesh.
symmetry_axisNoReflection plane axis for bilateral symmetry (default 'X' for sagittal symmetry).X
target_objectYesName of the target mesh object in the Blender scene.
max_face_countNoUpper face cap limit before rejecting detailing.
seam_thresholdNoMidline distance threshold in meters. Midline vertices within this distance to symmetry plane are clamped to zero displacement along the symmetry axis.
max_displacementNoStrict maximum displacement cap in meters per vertex.
max_vertex_countNoUpper vertex cap limit before rejecting detailing.
mask_vertex_groupNoOptional name of a vertex group on the mesh to restrict and modulate surface detailing weights [0.0..1.0].
preserve_topologyNoStrictly preserve mesh topology (vertex, edge, face count invariant).
subdivision_levelNoSubdivision level if subdivide_before_detail is true.
preserve_landmarksNoIf true, damps displacement near existing semantic landmarks to prevent landmark drift.
rollback_on_failureNoIf true, roll back mesh state bit-for-bit if limits are exceeded or regression occurs.
max_landmark_regressionNoMaximum allowed increase in landmark RMSE before triggering rejection and rollback.
subdivide_before_detailNoOptional pre-detail Catmull-Clark subdivision pass for coarse blockout geometry.
landmark_protection_radiusNoRadius in meters around landmarks within which displacement is damped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden, and it does disclose the key behavioral contract: landmark preservation, silhouette-regression limits against configured tolerances, strict topology invariants by default, and transactional rollback on failure. That is meaningful context beyond the schema properties, though it does not state permission requirements, cost/runtime of the multi-view objective, or what the failure response looks like.

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 states the operation, its scope, its feature set, and its three guarantees in that order, with no filler or restated title. It is dense but every clause corresponds to a real behavioral contract, though the packing of four guarantees into one sentence makes it slightly hard to scan.

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 30-parameter mutation tool with no annotations and no output schema, the description covers the two things an agent most needs to decide and call safely: the operation's scope and the guards that prevent damage (topology invariants, rollback, regression caps). It is thinner on how the optional reference-view machinery changes outcomes and says nothing about the return value, which is the main remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100 percent across all 30 parameters, so the schema already does the heavy lifting and a 3 is the baseline. The description nonetheless adds cross-parameter meaning that the schema cannot: that limits are 'bounded', that tolerances are 'configured' and enforced, and that preservation/rollback are defaults rather than extra steps, which tells the agent the negotiation between depth, tolerances, and caps that governs success.

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?

Names a specific verb and resource (applies bounded fine-scale anatomical surface detailing) and enumerates the exact feature types SCALES, RIDGES, FACETS, VEINS, which lets an agent match it to the feature_type enum without opening the schema. It does not distinguish itself from surface-related siblings such as inspect_surface_detail or align_normals, so it stops short of a 5.

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?

The phrases 'controlled, bounded' and 'explicitly designated target mesh' imply that callers must supply limits and a named target, and the description hints that the operation is guarded rather than free-form. There is no explicit when-to-use statement, no named alternative for merely inspecting or baking surface detail, and no note on when to prefer this over the sibling tools.

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