Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

flip_sprite

Flips an entire sprite horizontally or vertically to correct orientation or mirror pixel art in Aseprite.

Instructions

Flip the whole sprite horizontally or vertically.

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

Input Schema

NameRequiredDescriptionDefault
fileNo
directionYes

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 supply only a title, so the description carries the full burden of disclosing behavior for a mutation tool. It adds the useful qualifier "the whole sprite" (implying layers/frames are not individually targeted), but says nothing about whether the change is saved automatically, whether it is undoable, or what permissions/context are required.

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 short sentence that front-loads the action and scope with no filler. It is efficient, though its brevity contributes to the missing detail elsewhere rather than compensating for it.

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 no output schema, no meaningful annotations, and zero parameter documentation, the definition leaves too much unspecified for a mutation tool. An agent could not reliably know the accepted direction values or how the `file` argument interacts with the active sprite.

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 coverage is 0% for two parameters. The description implies the direction parameter accepts horizontal/vertical values but never gives the literal accepted strings, and it is entirely silent on the optional `file` parameter and what happens when it is omitted (presumably the active sprite).

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 specific verb and resource ("Flip the whole sprite") plus the two axes of variation, so the operation is immediately identifiable. It does not distinguish itself from the nearby transform siblings such as rotate_sprite, but the core action is unambiguous.

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 guidance on when to flip versus rotate or when to use this over other transform tools, and no prerequisites are stated. The agent must infer that a sprite must already be open/active for the operation to make sense.

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