Skip to main content
Glama
ext-sakamoro

Aseprite MCP Tools

by ext-sakamoro

draw_line

Draw straight lines on Aseprite canvas by specifying start and end coordinates, color, and thickness for pixel art creation.

Instructions

Draw a line on the canvas.

Args: filename: Name of the Aseprite file to modify x1: Starting x coordinate y1: Starting y coordinate x2: Ending x coordinate y2: Ending y coordinate color: Hex color code (default: "#000000") thickness: Line thickness in pixels (default: 1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
x1Yes
y1Yes
x2Yes
y2Yes
colorNo#000000
thicknessNo

Implementation Reference

  • The draw_line handler function, which validates inputs, generates a Lua script using LuaBuilder, and executes it via Aseprite.
    @mcp.tool()
    async def draw_line(filename: str, x1: int, y1: int, x2: int, y2: int, color: str = "#000000", thickness: int = 1) -> str:
        """Draw a line on the canvas.
    
        Args:
            filename: Name of the Aseprite file to modify
            x1: Starting x coordinate
            y1: Starting y coordinate
            x2: Ending x coordinate
            y2: Ending y coordinate
            color: Hex color code (default: "#000000")
            thickness: Line thickness in pixels (default: 1)
        """
        try:
            # Validate inputs
            file_path = validate_file_path(filename, must_exist=True)
            color = validate_color(color)
            
            if thickness < 1:
                raise ValidationError("thickness", thickness, "Thickness must be at least 1")
            
            # Build Lua script
            builder = LuaBuilder()
            builder.add_line('local spr = app.activeSprite')
            builder.if_condition('not spr')
            builder.add_line('error("No active sprite")')
            builder.end_if()
            builder.add_line()
            
            builder.begin_transaction()
            builder.draw_line(x1, y1, x2, y2, color, thickness)
            builder.end_transaction()
            builder.save_sprite()
            
            # Execute script
            cmd = get_command()
            success, output = cmd.execute_lua_script(builder.build(), str(file_path))
            
            return f"Line drawn successfully in {file_path}"
            
        except (ValidationError, AsepriteError) as e:
            return f"Failed to draw line: {e}"
        except Exception as e:
            return f"Unexpected error: {e}"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations exist, and the description does not disclose side effects, coordinate system, or behavior when parameters are out of bounds. Minimal transparency beyond the basic action.

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?

Succinct first sentence followed by a well-organized Args list. No extraneous information.

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?

Provides parameter details but lacks behavioral context (e.g., pixel replacement, canvas bounds). With no output schema, more completeness would be beneficial.

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?

The Args section thoroughly explains each parameter, including defaults for color and thickness, and the meaning of filename. This compensates for the 0% schema description coverage.

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 clearly states 'Draw a line on the canvas,' specifying the verb and resource. Among many drawing sibling tools, this uniquely identifies the action of drawing a line.

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 on when to use this tool versus alternatives like draw_path or draw_rectangle. No prerequisites or contextual cues provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.