Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

edit_armature_bones

Add, edit, or remove armature bones in Blender Edit Mode with rollback protection, atomic operations, hierarchy parenting, and connect flags.

Instructions

Edits armature bones in Edit Mode with rollback protection: add_bone, edit_bone, remove_bone, hierarchy parenting, connect flags.

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

Input Schema

NameRequiredDescriptionDefault
headNoHead [x, y, z] shortcut for single operation.
nameNoSingle bone name shortcut if 'operations' array is omitted.
rollNoBone roll in radians shortcut for single operation.
tailNoTail [x, y, z] shortcut for single operation.
actionNoSingle operation action shortcut if 'operations' array is omitted.
parentNoParent bone name shortcut for single operation.
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
operationsNoList of bone operations to apply atomically.
use_deformNoDeform flag for single operation.
use_connectNoConnect head to parent tail flag for single operation.
armature_nameYesTarget armature object name.
expected_snapshot_idNoOptimistic concurrency state hash. Mutation is rejected if state changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Rollback protection" gestures at the transactional/optimistic-concurrency behavior implied by expected_snapshot_id, but it is never explained (all-or-nothing on failure? rejection on state mismatch?), and remove_bone's destructive nature, the untrusted approved flag, and mode side effects are all undisclosed.

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 with no filler; the verb+resource leads and the operation list follows. The colon-separated list is dense but readable, and nothing is redundant.

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 a 13-parameter mutation tool with no annotations and no output schema, the description is too thin: it omits the two calling modes, atomicity semantics, credential/approval handling, and error behavior on snapshot mismatch. The rich schema compensates for parameter documentation but not for behavioral risk.

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 all 13 parameters, making the baseline 3. The description's mention of hierarchy parenting and connect flags loosely maps to parent/use_connect, but it adds no explanation of the dual calling convention (single-operation shortcuts vs. the operations array) or expected_snapshot_id mechanics.

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 names a specific verb and resource ("Edits armature bones") and enumerates the concrete operations: add_bone, edit_bone, remove_bone, plus parenting and connect flags. That is enough to distinguish it from create_armature or inspect_armature, though it never explicitly contrasts itself with them.

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?

"in Edit Mode" establishes a mode prerequisite, which is useful context an agent needs before calling. However, there is no guidance on when to choose this tool over inspect_armature or create_armature, and no stated exclusions or prerequisites such as object-must-exist or selection requirements.

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