Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

rotate_sprite

Rotate a whole sprite 90, 180, or 270 degrees clockwise without quality loss and one undo step. Pass a file to run headless.

Instructions

Rotate the whole sprite by 90, 180, or 270 degrees clockwise (lossless). One undo step. Headless: pass file.

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": {
      "degrees": "<degrees>"
    },
    "name": "rotate_sprite"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
degreesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

With no behavioral annotations supplied, the description does useful work by disclosing that the rotation is lossless and consumes exactly one undo step, which tells the agent the mutation is recoverable. It stops short of saying what happens on invalid degree values, whether an active sprite is required, or what the tool returns.

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?

Three terse clauses, front-loaded with the core operation, then the undo cost, then the headless usage note. No wasted words and nothing buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter rotation tool with no output schema, the description covers operation, allowed values, direction, reversibility, and headless usage. Missing only prerequisite/precondition context, which is minor here.

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 the description must carry parameter meaning, and it does: it restricts 'degrees' to 90/180/270 clockwise rather than any integer, and explains that 'file' targets a headless (non-UI) operation. The only gap is not naming 'file' explicitly as the headless path argument.

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?

States a specific verb (rotate), the object (the whole sprite), the allowed angles (90/180/270) and the direction (clockwise), so the agent knows exactly what operation is performed. It doesn't explicitly distinguish itself from flip_sprite or autocrop_sprite, but 'rotate' is unambiguous against those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Headless: pass file' sentence gives concrete usage context for one mode, and 'One undo step' hints at recovery via undo. However, it never states prerequisites (e.g. must a sprite be open or active) or when to prefer flip_sprite instead.

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