Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

set_frame_durations

Idempotent

Set all frames in a specified range to the same duration in milliseconds, keeping animation timing consistent across Aseprite frame sequences.

Instructions

Set every frame in [from_frame..to_frame] to ms milliseconds.

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": {
      "from_frame": "<from_frame>",
      "to_frame": "<to_frame>",
      "ms": "<ms>"
    },
    "name": "set_frame_durations"
  }
}

Input Schema

NameRequiredDescriptionDefault
msYes
fileNo
to_frameYes
from_frameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior2/5

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

The only annotation is idempotentHint=true; the description does not disclose that this mutates existing frame durations, what happens with out-of-range or reversed frame indices, or whether the change is persisted immediately. It adds little behavioral context beyond the annotation.

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 front-loaded sentence with no wasted wording. It communicates the action, scope, and unit efficiently.

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

Completeness3/5

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

For a simple mutation tool this covers the core operation, but with four parameters, zero schema descriptions, and no output schema, the undocumented 'file' parameter and missing edge-case behavior leave a clear gap.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It clarifies the inclusive range semantics for from_frame/to_frame and the millisecond unit for ms, but says nothing about the optional 'file' parameter or any parameter constraints.

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 states a specific verb ('Set') and resource ('frame durations') with an explicit inclusive range '[from_frame..to_frame]' and unit 'ms milliseconds'. This clearly distinguishes it from the singular sibling set_frame_duration, though it does not name that alternative explicitly.

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 explicit when-to-use guidance, no prerequisites, and no mention of when to choose set_frame_duration instead. The range syntax implies batch usage, but the agent must infer that comparison.

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