Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_semantic_landmarks

Sets, updates, or clears named 3D semantic landmarks and their FRONT, SIDE, and TOP reference-image coordinates on a Blender mesh for precise alignment and projection.

Instructions

Configure, update, or clear named 3D semantic landmarks and their corresponding 2D reference-image coordinates (FRONT, SIDE, TOP) on a designated mesh. Supports explicit landmarks such as snout_tip, horn_tips, wing_apexes, tail_tip, limb_joints, and claw_tips.

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

Input Schema

NameRequiredDescriptionDefault
actionNoLandmark operation: 'SET' (replace/set landmarks), 'UPDATE' (merge/update landmarks), 'REMOVE' (delete specified landmarks), or 'CLEAR' (remove all landmarks).SET
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
landmarksNoArray of semantic landmark definitions.
object_nameNoAlias for target_object.
target_objectYesName of the target mesh object in the Blender scene.
calibrated_camerasNoOptional mapping of view names ('FRONT', 'SIDE', 'TOP') to Blender camera names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden, but it only implies mutation and does not disclose that CLEAR removes all landmarks, that SET replaces existing entries, permission/consent requirements, or whether changes are reversible. It also omits any warning about the deprecated `approved` parameter, leaving the agent without operational context for a scene-modifying tool.

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?

Two tight sentences with the core action front-loaded and no filler. The second sentence's examples are useful but border on redundant; overall the text is well-structured and easy to parse.

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

Completeness2/5

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

For a seven-parameter mutation tool with nested landmark objects, no annotations, and no output schema, the description is too thin: it does not cover return behavior, side effects, prerequisites, or interaction with detection/inspection siblings. The rich schema helps with parameter semantics but cannot compensate for missing operational context.

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 schema already documents every parameter, including action enum semantics, landmark fields, and camera mapping. The description's landmark-name and view examples largely duplicate schema content and add no new meaning; baseline 3 applies.

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 set (configure, update, clear) and a precise resource (named 3D landmarks plus 2D FRONT/SIDE/TOP coordinates on a designated mesh), so the operation is unambiguous. It does not explicitly distinguish itself from siblings like detect_semantic_landmarks or inspect_semantic_landmarks, so it falls 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No sentence states when to choose this tool over detect_semantic_landmarks, inspect_semantic_landmarks, or guide_mesh_landmarks, nor are there prerequisites or exclusions. The four actions are explained in the schema, not in the description, so the description provides no usage 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