Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

apply_timing

Set frame durations from a preset over a tag or frame range to create easing, hold, or bounce timing in Aseprite animations, with one undo step.

Instructions

Set frame durations from a preset, over a tag or a frame range (every frame by default). ease_in starts slow and speeds up, ease_out slows to a stop, ease_in_out does both, hold keeps the last frame on screen, and bounce hangs at the middle and snaps through both ends. base_ms is the quickest frame and strength how many times longer the slowest lasts. One undo step. Headless: pass file.

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": {
      "preset": "<preset>"
    },
    "name": "apply_timing"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
fileNo
presetYes
base_msNo
strengthNo
to_frameNo
from_frameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations carry only a title, so the description must do the behavioral work, and it does deliver meaningful context: "One undo step" discloses undo grouping, and "Headless: pass ``file``" discloses the operating mode requirement. It does not say whether existing timing is overwritten or how tag and frame-range arguments interact when both are supplied, which is the notable remaining 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?

Front-loads the core action and scope before enumerating preset semantics, and every clause carries information. It is dense with backtick-quoted parameter names, which is efficient but makes the preset enumeration slightly hard to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter mutation tool with no output schema and no substantive annotations, the description covers the action, scope default, preset vocabulary, key numeric parameters, undo behavior, and headless mode. What remains thin is the interaction between tag and frame range and any indication of what happens on conflicting or empty selection.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate and largely does: it defines ``base_ms`` (quickest frame), ``strength`` (how many times longer the slowest lasts), the meaning of every ``preset`` value, ``tag`` and frame-range targeting, and ``file`` for headless use. Only ``from_frame``/``to_frame`` are covered implicitly rather than named, and types/bounds remain undocumented.

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?

States a specific verb and resource ("Set frame durations from a preset") and immediately scopes the target: a tag or a frame range, defaulting to every frame. The named preset vocabulary makes clear exactly what kind of timing operation this is, which is enough to tell it apart from frame-adding or animation siblings.

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?

Implies usage through the default scope ("every frame by default") and the headless note ("pass ``file``"), which tells the agent how to invoke it outside an interactive session. However, it gives no explicit when-to-use vs. when-not guidance and no reference to alternative timing or animation tools, so the agent must infer the boundary.

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