Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

set_keyframe_interpolation

Configure animation F-Curves on a Blender object by setting keyframe interpolation modes, adding or removing curve modifiers, and managing Action Slots.

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": "set_keyframe_interpolation"
  }
}

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

B3.2/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and falls short: it does not say whether existing keyframes are overwritten, whether changes are undoable, what happens when a named object has no F-Curves, or what errors occur. The word 'configure' hints at mutation but nothing about side effects or reversibility is disclosed.

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 that wastes no words and puts the scope up front. The dense parenthetical lists of enum values are mildly redundant with the schema but aid scanning.

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

Completeness5/5

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

For an eleven-parameter mutation tool with no annotations and no output schema, the definition is missing behavioral detail (destructive action, undo/error handling), prerequisites, and when-to-use routing. Those gaps are material for an agent that must decide safely whether to call it.

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 every one of the eleven parameters is already documented, and the description's mention of interpolation modes, modifiers, and slots largely mirrors enum values in the schema. It adds no syntax or interaction details (e.g. how array_index -1 behaves with CONSTANT interpolation) beyond what the schema states, making the baseline 3 appropriate.

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 concrete verb ('Configure') and enumerates the resources it touches: F-Curves, keyframe interpolation modes, curve modifiers, and Blender 5.2 Action Slots on an animated object. It is clearly distinguishable from siblings like insert_keyframe or delete_keyframe, though it never explicitly contrasts itself with configure_animation_curve or manage_keyframe.

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 statement of when to use this tool versus insert_keyframe, manage_keyframe, or configure_animation_curve, and no prerequisites such as 'the object must already have animation data'. The action enum implies several distinct use cases but the description gives no guidance on selecting among them.

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