Skip to main content
Glama

create_keyframe

Insert a keyframe on an object at a specified frame and data path to animate its properties over time in Blender.

Instructions

Insert a keyframe on an 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": {
      "name": "<name>",
      "data_path": "<data_path>"
    },
    "name": "create_keyframe"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
frameNo
indexNo
data_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 but provides almost nothing. It does not say what happens when a keyframe already exists at the given frame (overwrite vs. duplicate), whether index controls insertion order, or whether the operation is reversible — all material for a mutating tool.

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?

The single sentence is front-loaded and free of waste, but its brevity reflects under-specification rather than efficiency. Nothing is redundant; there simply is very little content to structure.

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?

An output schema exists, so return values need not be explained, but for a four-parameter mutation tool with zero schema documentation the description leaves critical gaps: parameter meaning, overwrite behavior, and prerequisites. It is not complete enough for reliable invocation.

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

Parameters1/5

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

Schema description coverage is 0% across four parameters, including the required 'data_path' and the ambiguous 'index' (default -1) and 'frame' (nullable). The description mentions none of them, so an agent has no idea what 'data_path' points to or what index -1 means.

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 specific verb and resource: 'Insert a keyframe on an object.' An agent can immediately tell this is the keyframe-creation operation. It does not, however, differentiate itself from siblings such as set_keyframe or remove_keyframe, so the agent must infer which one applies.

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 versus alternatives (set_keyframe, remove_keyframe), nor any stated preconditions such as requiring an existing object or animation data. The agent gets only the bare action, with usage left entirely to inference.

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