Skip to main content
Glama
Sign In
Inochi Creator MCP

Inochi Creator MCP

by ozekimasaki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

creator_add_keyframe

Add or update a keyframe at the current frame for a specified parameter, enabling precise control over animation curves in Inochi Creator.

Instructions

Add or update a keyframe on the current animation at the current frame.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "creator_add_keyframe"
  }
}

Input Schema

NameRequiredDescriptionDefault
axisNo0 = X, 1 = Y (default 0)
nameNoParameter name
uuidNoParameter UUID
valueNoKeyframe value; defaults to the parameter's current value

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries full behavioral burden. It discloses that the tool can add or update, implying idempotent behavior at a given frame, but omits prerequisites (active animation, parameter existence), side effects, and error behavior. This is a significant gap for a mutation tool.

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?

A single concise sentence with no wasted words. It front-loads the core operation and context efficiently.

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 description lacks important context: what a keyframe means in this workflow, whether to use name or uuid, what happens if a keyframe already exists, and any prerequisites. Without an output schema or annotations, the agent has limited information for reliable invocation.

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?

The schema provides descriptions for all four parameters (100% coverage), so the baseline is 3. The description adds no further parameter details beyond what the schema already includes.

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?

The description clearly states the action ('Add or update a keyframe') and its scope ('on the current animation at the current frame'). This distinguishes it from sibling tools like creator_remove_keyframe.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives context (current animation, current frame) but does not explicitly compare to alternatives or state when not to use it. There is no reference to sibling tools like creator_set_parameter or creator_remove_keyframe.

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