Aseprite-MCP

by iborymagic

Overview Schema Source Related Servers Discussions Admin

TypeScript

normalize_animation_speed

Set all frame durations in an animation to a consistent speed by specifying a target duration in seconds.

Instructions

Normalizes all frame durations to a single target duration (in seconds)

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": {
      "saveOutput": "<saveOutput>",
      "targetDuration": "<targetDuration>",
      "inputFile": "<inputFile>"
    },
    "name": "normalize_animation_speed"
  }
}

Input Schema

Name	Required	Description	Default
`inputFile`	Yes
`saveOutput`	Yes
`targetDuration`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jul 5, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are present, so the description must disclose behavior. It does not mention whether the tool modifies files in place, creates new output (though saveOutput hints), or any side effects like overwriting.

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 description is concise (one sentence) but lacks details that could be added without verbosity, such as parameter explanations.

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?

Given no output schema and minimal description, the tool lacks completeness. The agent cannot infer return values or exact behavior beyond basic normalization.

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

Parameters2/5

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

Schema description coverage is 0%, yet the description only explains targetDuration (seconds) and omits inputFile and saveOutput, leaving two parameters with no added meaning.

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 clearly states the tool normalizes all frame durations to a single target duration in seconds, distinguishing it from siblings like get_frame_info or export_frames.

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 guidance is provided on when to use this tool versus alternatives, nor are prerequisites or when-not scenarios mentioned.

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