Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_animation_curve

Configures F-Curves on animated objects, setting keyframe interpolation, adding or removing curve modifiers, and managing Blender Action Slots for precise animation control.

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

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.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Configure" implies mutation, but the text does not say what is changed or destroyed, whether changes are reversible, what permissions are needed, or what a response looks like.

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 enumerates capabilities without filler. It is dense but well structured and does not repeat itself.

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?

The tool has 11 parameters, multiple actions, no annotations, and no output schema, so the description needs to explain action-dependent behavior and safety. It lists capabilities but leaves out how actions differ, required parameter combinations, and mutation consequences.

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 coverage is 100% and the schema already documents all 11 parameters, including enums and examples. The description names supported interpolation modes, modifier types, and Action Slots, but mostly restates categories already present in the schema rather than adding syntax or selection logic.

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: configuring animation F-Curves, interpolation modes, curve modifiers, and Action Slots on an animated object. It implicitly separates animation-curve work from geometry-curve siblings, though it does not name an alternative 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?

No explicit when-to-use or when-not-to-use guidance, no alternatives, and no conditions for choosing among the available actions. The only scoping cue is "on an animated object," which is implied rather than instructive.

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