Skip to main content
Glama
Sign In
Aseprite MCP Tools

Aseprite MCP Tools

by NosytLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_frame_duration

Modify the display time of a specific frame in an Aseprite animation by setting its duration in milliseconds.

Instructions

Set the duration of a frame in milliseconds.

Args: filename: Name of the Aseprite file to modify frame_index: Frame index starting at 1 duration_ms: 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": {
      "filename": "<filename>",
      "frame_index": "<frame_index>",
      "duration_ms": "<duration_ms>"
    },
    "name": "set_frame_duration"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
duration_msYes
frame_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Indicates it modifies an Aseprite file (mutation), but without annotations the description should state if changes are reversible, require saving, or have side effects. Adequate for a straightforward operation.

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?

Brief and structured as an args list. No unnecessary words. Could be slightly more informative but efficient.

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?

No output schema, no annotations, 0% schema coverage. Description provides basic info but lacks constraints (e.g., valid duration range, error handling). Sufficient for simple tool.

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 coverage is 0%, so description must explain parameters. It does: filename, frame_index (starting at 1), duration_ms (milliseconds). Adds meaning beyond type and required.

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?

Clearly states the tool sets the duration of a frame in milliseconds, with specific verb and resource. Distinguishes from siblings like 'set_frame_duration_all' which targets all 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 on when to use this tool versus alternatives (e.g., 'set_frame_duration_all' or 'set_frame'). Does not mention prerequisites or constraints.

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