Skip to main content
Glama
dwgx

Blender Copilot MCP Server

by dwgx

anim_insert_keyframes_batch

Insert multiple keyframes for a Blender object in one call by specifying frame, data path, and value for each keyframe.

Instructions

Insert multiple keyframes at once.

Args: object_name: Target object name keyframes: List of dicts, each with: - frame (int): Frame number - data_path (str): Property path - value: Value to set (single float or [x,y,z] list) - index (int, optional): Channel index (-1 for all)

Example keyframes: [ {"frame": 1, "data_path": "location", "value": [0, 0, 0]}, {"frame": 30, "data_path": "location", "value": [5, 0, 2]}, {"frame": 60, "data_path": "location", "value": [0, 0, 0]} ]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyframesYes
object_nameYes
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. Fails to disclose error handling, overwrite behavior, channel indexing details, or side effects beyond structure of keyframes.

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

Conciseness5/5

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

Description is well-structured with purpose first, then argument details, then example. Each sentence adds value, no redundancy or fluff.

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?

Missing behavioral details like return values, error conditions, and confirmation of insertion. Given complexity and lack of output schema, description is incomplete for an agent to fully predict behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description fully defines parameters: 'object_name' as target, 'keyframes' as list of dicts with required fields and optional index. Example demonstrates structure and usage, adding essential meaning.

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

Purpose5/5

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

Description clearly states 'Insert multiple keyframes at once', specifying verb and resource. Differentiates from sibling 'anim_insert_keyframe' which handles single keyframe insertion.

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 guidance on when to use this tool vs alternatives like 'anim_insert_keyframe'. Does not provide when-not scenarios or usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dwgx/blender-copilot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server