Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_bone_constraint

Configures Pose Mode bone constraints in Blender—IK, Limit Rotation, and Copy Transforms—so you can add, remove, or update rig behavior.

Instructions

Configures Pose Mode constraints on armature bones: Inverse Kinematics (IK), Limit Rotation, Copy Transforms.

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": {
      "armature_name": "<armature_name>",
      "bone_name": "<bone_name>"
    },
    "name": "configure_bone_constraint"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoAction: ADD new constraint, REMOVE existing, or UPDATE properties (defaults to ADD).ADD
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
bone_nameYesName of the pose bone to constrain.
influenceNoConstraint influence factor between 0.0 and 1.0.
pole_angleNoPole angle in radians for IK constraints.
chain_countNoIK chain length (number of bones up the hierarchy; 0 solves all ancestor bones).
owner_spaceNoCoordinate space of the owner bone.
pole_targetNoOptional pole target object for IK constraints.
target_boneNoTarget subtarget bone name on target armature.
target_spaceNoCoordinate space of the target object/bone.
armature_nameYesName of the armature containing the target bone.
target_objectNoTarget object name for constraints that track objects.
pole_subtargetNoOptional pole target bone name for IK constraints.
constraint_nameNoOptional explicit constraint name.
constraint_typeNoType of bone constraint to configure.IK
expected_snapshot_idNoOptimistic concurrency state hash of the armature.
limit_rotation_settingsNoSettings for LIMIT_ROTATION: use_limit_x/y/z (bool), min_x/y/z (float), max_x/y/z (float).

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?

No annotations are provided, so the description carries the full behavioral burden. It implies mutation and identifies the constraint types, but does not disclose permissions, required Pose Mode/edit state, reversibility, effects of ADD vs REMOVE vs UPDATE, or concurrency behavior.

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?

The description is a single front-loaded sentence with no filler, and the key resource and supported constraint types are stated immediately. Its brevity is efficient, though the same brevity contributes to missing behavioral guidance.

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?

This is a complex mutation tool with 18 parameters, nested settings, no annotations, and no output schema. The schema is rich, but the description does not cover operational prerequisites, action semantics, concurrency expectations, or the deprecated approval flag, leaving important context absent.

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 each of the 18 parameters in detail. The description adds only the high-level list of supported constraint types, which the schema enum also supplies, so the baseline of 3 is appropriate.

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 gives a specific verb (Configures), resource (Pose Mode constraints on armature bones), and enumerates the supported constraint types. It is clearly distinguishable from unrelated configure_* siblings by its bone-constraint scope, though it does not explicitly name alternative tools.

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?

The definition states what the tool configures but gives no when-to-use guidance, no when-not-to-use conditions, and no alternatives. An agent must infer that this tool applies only to armature bone constraints in Pose Mode.

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