Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

set_frame_duration

Idempotent

Set how long a frame lasts in milliseconds for Aseprite animations. Use it to control timing per frame when building or adjusting pixel art sequences.

Instructions

Set frame number's duration in 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": {
      "number": "<number>",
      "ms": "<ms>"
    },
    "name": "set_frame_duration"
  }
}

Input Schema

NameRequiredDescriptionDefault
msYes
fileNo
numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations only supply idempotentHint=true and a title; there is no readOnly/destructive hint. The description adds nothing about whether the change is reversible, whether it affects only the given frame, or what happens if the frame index is out of range, so the burden of disclosure is unmet 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, but the terseness crosses into under-specification rather than true efficiency.

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?

With three parameters, zero schema description coverage, no output schema, and no annotations covering safety, this description is too thin. Key facts an agent needs — the meaning of 'file', index base, and behavior on invalid frames — are absent.

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%, so the description must compensate. It clarifies 'number' as a frame and 'ms' as milliseconds, but the third parameter 'file' is never mentioned, and it does not say whether the frame index is 0-based or 1-based.

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?

States a specific verb and resource ('Set frame number's duration') plus the unit (milliseconds), so an agent can tell what the tool mutates. It does not distinguish itself from the sibling set_frame_durations, which is presumably the multi-frame/batch variant, leaving that choice to inference.

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 when-to-use guidance, no precondition (does the frame need to exist?), and no mention of the plural sibling as the alternative for setting several durations. The agent is left to guess at routing and prerequisites.

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