Skip to main content
Glama
Sign In
Aseprite MCP

Aseprite MCP

by MalloyTheDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

flip_sprite

Flip an entire sprite horizontally or vertically to change its orientation for pixel art editing and animation.

Instructions

Flip the entire sprite. direction: "horizontal" or "vertical".

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

Input Schema

NameRequiredDescriptionDefault
filenameYes
directionNoDefault: "horizontal".horizontal

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.10.0
    • addedInput schema / properties / direction / description
      Added value: +"Default: \"horizontal\"."
    • removedInput schema / properties / direction / title
      Removed value: -"Direction"
    • removedInput schema / properties / filename / title
      Removed value: -"Filename"
    • removedInput schema / title
      Removed value: -"flip_spriteArguments"
  2. First observedv0.7.0

TDQS

B3.1/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=false and openWorldHint=false, so the write nature is known. The description does not add behavioral context such as whether the change is saved automatically, whether the sprite file must exist, or whether the operation is reversible.

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 two short sentences, front-loaded with the core action and followed by the key parameter constraint. It is appropriately sized and contains no wasted words.

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 with no output schema, the description covers the operation and direction values. It omits file-handling details such as whether the filename refers to an existing sprite or how the result is persisted, which leaves relevant context gaps.

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 50%. The description supplies the allowed direction values ('horizontal' or 'vertical'), which the schema only partially indicates through a default. The required filename parameter is not described in either place, so the description only partially compensates for the coverage gap.

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 clearly states a specific verb (Flip) and resource (entire sprite), and the direction parameter indicates the operation's axis. It does not explicitly distinguish itself from similarly named siblings such as mirror_layer or rotate_sprite, so it falls short of the top score.

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 is given on when to use this tool versus alternatives like rotate_sprite or mirror_layer. The implied usage is obvious but not stated explicitly, leaving the agent to infer context.

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