Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

manage_action_slots

Configure animation F-Curves, keyframe interpolation modes, curve modifiers, and Blender 5.2 Action Slots on an animated object to control timing and slot behavior.

Instructions

Configure animation F-Curves, keyframe interpolation modes (CONSTANT, LINEAR, BEZIER), curve modifiers (CYCLES, NOISE, LIMITS), and Blender 5.2 Action Slots on an animated object.

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": {
      "object_name": "<object_name>"
    },
    "name": "manage_action_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoAnimation curve action to perform.set_interpolation
easingNoKeyframe easing mode.AUTO
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
data_pathNoAnimation property path (e.g. 'location', 'rotation_euler', 'scale').
slot_nameNoSlot name for Blender 5.2 Action Slots.
array_indexNoChannel array index (0 for X, 1 for Y, 2 for Z, or -1 for all channels).
object_nameYesName of the target animated object.
slot_id_typeNoTarget ID type for ActionSlot creation (defaults to 'OBJECT').OBJECT
interpolationNoKeyframe interpolation mode.BEZIER
modifier_typeNoF-Curve modifier type (e.g. CYCLES, NOISE, GENERATOR, LIMITS).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/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 largely drops it. It never says that add_modifier/remove_modifier mutate and can destroy existing curve data, that list_fcurves is a read, whether changes are undoable, or what the response looks like. The fact that it is a mutating tool with per-action risk profiles is left entirely undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single efficient sentence with no padding, which is good, but the limited space is spent re-listing enum values already present in the schema while the most important fact - the action dispatch model - is omitted. Front-loading is fine; content allocation is poor.

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?

For an 11-parameter, five-action tool with no annotations and no output schema, the description is far too thin. It gives no action-to-parameter mapping, no indication of which operations are reads vs. mutations, and no return-value context (particularly needed for list_fcurves, which is the only query action).

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 explains every parameter, including the deprecated/untrusted 'approved' flag and the array_index conventions; baseline 3 applies. The description adds nothing beyond restating enum values (CONSTANT, LINEAR, BEZIER; CYCLES, NOISE, LIMITS) that the schema already lists, and it omits any explanation of how parameter relevance changes per action.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Configure' plus concrete resources (F-Curves, interpolation modes, curve modifiers, Action Slots) gives a usable sense of the domain, but the description never reveals that this is a multi-action dispatcher driven by the 'action' enum (set_interpolation, add_modifier, remove_modifier, manage_slot, list_fcurves). It also fails to distinguish itself from siblings such as manage_fcurve and manage_keyframe, which read as overlapping in scope.

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 at all: nothing says when to pick this tool over manage_fcurve, manage_keyframe, or manage_timeline_markers, and nothing explains which of the five action values to choose for a given goal. Usage must be reverse-engineered entirely from the schema enum.

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