Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

manage_fcurve

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

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_fcurve"
  }
}

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. It never states that this mutates scene data, whether changes are reversible/undoable, what happens to existing keyframes or modifiers, or what the response contains. For a multi-action mutation tool with zero annotation coverage, this is a substantial gap.

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 with no filler, and the resource is named first. It is dense but every clause maps to a real capability, though the packed enumeration slightly hurts scannability.

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?

For an 11-parameter, five-action tool with no annotations and no output schema, the description is thin: it does not explain which parameters apply to which action (e.g. slot_name only for manage_slot, modifier_type only for add/remove_modifier). The 100% schema coverage mitigates this, but action-parameter coupling is left undocumented.

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 parameter is already documented, and the description adds essentially nothing beyond restating the enum values (CONSTANT, LINEAR, BEZIER, CYCLES, NOISE, LIMITS) that the schema already lists. Baseline 3 applies since the schema does the heavy lifting.

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 ('Configure') and resource ('animation F-Curves') and enumerates the domains it covers: interpolation modes, curve modifiers, and Action Slots. It does not mention two of the five schema actions (list_fcurves, remove_modifier), so the full scope is only visible by opening the schema, but the core 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 to use this tool versus siblings like manage_keyframe or manage_action_slots, and no guidance on which of the five 'action' values to select for a given goal. The agent must infer routing and action selection 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