Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

guide_mesh_landmarks

Deforms a mesh toward calibrated semantic landmarks using multi-view reference images and bounded back-projection, preserving topology and rolling back when error or silhouette tolerances fail.

Instructions

Deform a designated mesh toward calibrated 2D/3D semantic landmarks using bounded multi-view back-projection with smooth radial influence and Laplacian regularization. Requires measurable landmark error reduction while enforcing silhouette regression tolerances across protected views. Preserves topology by default.

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

Input Schema

NameRequiredDescriptionDefault
viewsNoOptional list of 1 to 3 calibrated reference view configurations for silhouette regression monitoring.
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
landmarksNoOptional list of landmarks to configure or override for this guidance run.
objectiveNoLandmark optimization objective metric.WEIGHTED_LANDMARK_RMSE
step_sizeNoGuidance step size / learning rate factor in [0.01, 1.0].
object_nameNoAlias for target_object.
falloff_typeNoSpatial falloff function for landmark influence.SMOOTH
target_objectYesName of the target mesh object in the Blender scene.
max_face_countNoUpper face cap limit before rejecting guidance.
max_iterationsNoMaximum number of guidance iterations.
influence_radiusNoRadius of influence around landmark vertices in meters.
max_displacementNoMaximum allowed displacement cap in meters per vertex.
max_vertex_countNoUpper vertex cap limit before rejecting guidance.
preserve_topologyNoStrictly preserve mesh topology (vertex, edge, face count).
laplacian_smoothingNoLaplacian surface smoothing factor to maintain mesh fairness.
min_error_reductionNoMinimum required landmark RMSE reduction to accept deformation.
rollback_on_failureNoIf true, transactionally roll back mesh if objective does not improve or tolerances are violated.

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, the description carries the full behavioral burden and discloses substantial traits: deformation, bounded multi-view back-projection, radial influence, Laplacian regularization, required error reduction, silhouette regression enforcement, and topology preservation by default. It still omits operational details such as in-place mutation behavior, rollback behavior, and required permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three dense sentences with no wasted wording, and it front-loads the core deformation purpose before stating acceptance constraints and topology behavior. The structure is appropriate for a complex mesh-guidance tool.

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 an 18-parameter mutation tool with no annotations and no output schema, the description covers core behavior and constraints but leaves important gaps. It does not explain return values, failure behavior, rollback semantics, or prerequisites that would help an agent call it correctly.

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 18 parameters thoroughly. The description adds conceptual context for landmarks, views, radial influence, smoothing, and tolerances, but it does not add parameter-specific semantics 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 states a specific verb and resource: 'Deform a designated mesh toward calibrated 2D/3D semantic landmarks.' It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as configure_semantic_landmarks, detect_semantic_landmarks, or optimize_mesh_silhouette.

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?

Usage is implied by the purpose and the mention of calibrated landmarks and silhouette tolerances, but the description never explicitly says when to use this tool versus alternatives. It also omits prerequisites such as whether landmarks must first be detected or configured.

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