Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_handle_type

Set the handle type for every control point on a named curve to AUTO, VECTOR, ALIGNED, or FREE_ALIGN, controlling how the curve bends in Blender.

Instructions

Set the handle type for all control points of a curve.

Args: curve_name: Name of the curve object. handle_type: Handle type - AUTO, VECTOR, ALIGNED, or FREE_ALIGN.

Returns: Dict with confirmation of handle type change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
curve_nameYes
handle_typeNoAUTOMATIC

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / handle_type / default
      Previous value: -"AUTO"New value: +"AUTOMATIC"
    • addedInput schema / properties / handle_type / enum
      Added value: +[
+  "ALIGNED",
+  "AUTO",
+  "AUTOMATIC",
+  "FREE",
+  "FREE_ALIGN",
+  "TOGGLE_FREE_ALIGN",
+  "VECTOR"
+]
  2. Addedv1.2.2

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the important mutation scope ('all control points of a curve' – a bulk, non-undoable-by-this-tool change) and that it returns a confirmation dict, which is genuine context. It says nothing about required state (edit vs object mode), permissions, or whether the change is reversible.

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 purpose is front-loaded in a single sentence, followed by conventional Args/Returns sections with no padding. Slightly boilerplate, but every line carries information and nothing is wasted.

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?

An output schema exists, so the return value need not be explained further, and the description is adequate for a simple, low-risk two-parameter curve edit. It nonetheless leaves gaps for a no-annotation mutation tool: no required object state, no account of the omitted enum behaviors (FREE, TOGGLE_FREE_ALIGN), and no note on side effects or undoability.

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 0%, so the description must compensate and it partly does by naming both parameters and describing curve_name and handle_type. However, it lists only four of the seven enum values (AUTO, VECTOR, ALIGNED, FREE_ALIGN) and omits AUTOMATIC – which the schema marks as the default – along with FREE and TOGGLE_FREE_ALIGN, leaving an agent with an incomplete and slightly misleading option set.

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 states a specific verb and resource ('Set the handle type') and identifies the exact target scope ('all control points of a curve'), so an agent can distinguish this from mesh or object-level sibling tools. It does not explicitly contrast with curve siblings like switch_curve_direction or smooth_curve, but the purpose is unambiguous.

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 guidance on when this tool should be used versus alternatives, nor any prerequisite or exclusion stated – nothing about edit mode, curve selection, or whether the object must be a Bezier/NURBS curve for handles to exist. The only implied usage is 'you have a curve whose handles you want to change'.

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