Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_bone_property

Set a property on an armature bone, such as roll, length, or use_deform, to control rig behavior. Returns confirmation with the bone name, property, and new value.

Instructions

Set a property on a bone in an armature.

Args: armature_name: Name of the armature object. bone_name: Name of the bone. property: Property to set. One of: roll, length, use_connect, use_deform, envelope_distance, head_radius, tail_radius, use_inherit_rotation, use_local_location. value: Value to set the property to.

Returns: Confirmation dict with bone name, property, and new value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes
propertyYes
bone_nameYes
armature_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / property / enum
      Added value: +[
+  "envelope_distance",
+  "head_radius",
+  "length",
+  "roll",
+  "tail_radius",
+  "use_connect",
+  "use_deform",
+  "use_inherit_rotation",
+  "use_local_location"
+]
  2. First observedv0.1.0

TDQS

B3.2/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 confirms a return structure, but says nothing about permission/mode requirements, what happens on invalid property/value pairs, or reversibility of the mutation, and the return shape is likely already covered by the output schema. For a mutation tool with zero annotation coverage this is thin.

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?

Front-loaded one-line purpose followed by a compact Args/Returns block; every line earns its place with no padding. Slightly verbose in repeating the property enum already present in the schema.

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

Completeness4/5

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

For a low-moderate complexity setter with an output schema present, the description covers purpose, all parameters, and the confirmation return, which is adequate. Missing mode/prerequisite context and per-property value typing keep it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does document all four parameters with intent (armature_name, bone_name, property, value). The gap is 'value': the description never indicates that the expected type varies by property (bool flags vs. float radii), which is the main ambiguity left for the caller.

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 ('Set a property on a bone in an armature') and enumerates the settable properties, making it easy to distinguish from sibling tooling like add_bone or set_modifier_property. It lacks an explicit naming of what it is not, so it stops 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?

There is no when-to-use guidance, no mention of required context (edit vs. pose mode, existing armature/bone), and no comparison to related tools such as set_pose or set_modifier_property. The agent must infer usage entirely.

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