Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_armature

Creates a Blender armature object and its datablock with specified location, rotation, and scale transforms, enabling scene setup for rigging workflows.

Instructions

Creates a new Armature object and underlying datablock in the scene with position, rotation, and scale transforms.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_armature"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName for the new armature (defaults to 'Armature').Armature
scaleNoArmature scale [x, y, z].
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
locationNoArmature 3D location [x, y, z].
rotationNoArmature Euler rotation [x, y, z] in radians.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/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 it only establishes that a scene datablock is created. It says nothing about whether the new object becomes active/selected, whether it is linked to the active collection, whether the operation is undoable, or how the deprecated 'approved' flag interacts with execution.

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?

A single front-loaded sentence with no filler; the verb and the created resource appear first and every clause (datablock, scene, transforms) contributes information.

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 mutation tool with zero annotation coverage and no output schema, the description covers what is created and where but omits post-creation state (selection, active object, collection linkage) and what identifier is returned. It is minimally viable rather than complete.

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 all six parameters are already documented in the schema. The description's mention of position, rotation, and scale maps onto location/rotation/scale but adds no units, defaults, or formatting detail beyond what the schema states.

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?

States a specific verb and resource — creating an Armature object plus its underlying datablock — and scopes it to the scene with transforms. That differentiates it from siblings like edit_armature_bones, bind_armature_mesh, and inspect_armature, though it never names them explicitly.

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?

There is no when-to-use or when-not-to-use guidance: nothing says this should precede edit_armature_bones, that it works in object mode, or what distinguishes it from create_primitive/create_curve. The agent must infer usage from the tool name alone.

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