Skip to main content
Glama
Sign In
Aseprite Asset MCP

Aseprite Asset MCP

by jdsalasca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

generate_motion_pack

Generate idle, walk, run, jump, or attack cycles from a static or animated sprite. Create deterministic animation packs for game-ready pixel art assets.

Instructions

Generate a deterministic idle, walk, run, jump, or attack cycle from a static or animated sprite.

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": {
      "input_filename": "<input_filename>",
      "output_filename": "<output_filename>",
      "motion": "<motion>"
    },
    "name": "generate_motion_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNo
formatNo
framesNo
motionYes
delay_msNo
amplitudeNo
input_filenameYes
output_filenameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose that the generation is 'deterministic', which is a meaningful trait, and it clarifies input compatibility (static or animated sprite). However, it omits other important behaviors such as whether it modifies the input, output format details, or any limitations on sprite size or complexity. The determinism mention adds some value beyond the schema but coverage is minimal.

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?

The description is a single, compact sentence that front-loads the primary purpose. There is no fluff, filler, or redundant phrasing. Every word contributes to the core message. It is an excellent example of concise, well-structured documentation.

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?

For a tool with 8 parameters, a specific motion-generation task, and no output schema, the description is severely incomplete. It does not describe the output file structure, how determinism is controlled (e.g., seed usage), any prerequisites (e.g., sprite orientation, pivot points), or typical use cases. An agent would struggle to know what to expect or how to configure parameters effectively.

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%, meaning the description does not mention any of the 8 parameters. It fails to explain what 'seed', 'amplitude', 'delay_ms', etc. do, forcing the agent to rely solely on the schema's defaults and enums. Since coverage is zero, the description should compensate by clarifying parameter roles, but it does so not at all. This is a significant gap.

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?

The description states a specific verb ('Generate'), a clear resource ('from a static or animated sprite'), and the output type ('idle, walk, run, jump, or attack cycle'). It distinguishes itself from sibling tools like generate_sprite_hitboxes or generate_normal_map by naming the exact motion cycle types. This is a precise, unambiguous statement of what the tool does.

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?

The description does not provide any guidance on when to use this tool versus alternatives. It doesn't mention scenarios where this tool is appropriate or inappropriate, nor does it reference sibling tools or workflow steps. The agent would have to infer usage from the name and the generic description, which is insufficient given the wide range of animation-related tools.

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