Skip to main content
Glama
Sign In
Aseprite Asset MCP

Aseprite Asset MCP

by jdsalasca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_frame

Sets the active animation frame in an Aseprite file by one-based index to preview or edit a specific frame.

Instructions

Set the active animation frame by one-based index.

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>"
    },
    "name": "set_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
frame_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

The description implies a mutation (setting something), which is accurate given the tool name. However, with no annotations provided, the description carries the full burden. It doesn't disclose side effects (e.g., whether previous frame state is lost, whether undo is possible) or any permissions needed. But the one-based index note is a small behavioral cue.

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 sentence that is clear and front-loads the core action. No fluff.

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?

The tool operates on an animation frame, but the description doesn't mention what 'filename' points to, whether the sprite must already be loaded, or how the active frame relates to layers/cels. Given the large sibling set with related tools (like add_frame, delete_frame), a brief context note would improve completeness.

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 coverage is 0%, so the description must explain the parameters. It explains frame_index as one-based, which adds crucial semantic meaning beyond the schema (which only says integer >0). However, it doesn't explain what 'filename' refers to (the animation file? sprite? ) and how to obtain it. So partial compensation.

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 clear verb ('set') and a specific resource ('active animation frame') with a parameter ('by one-based index'). It distinguishes from sibling tools like add_frame/set_frame_duration because it specifically targets the active frame, not adding or timing 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?

It says to set the active frame, but doesn't explain when to use it compared to alternatives like add_frame or duplicate_frame_range. There's no mention of prerequisites like an open sprite or animation context, and no guidance on when to avoid it.

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