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}"
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool modifies a file ('modify'), implying mutation, but doesn't disclose behavioral traits like whether changes are saved automatically, if there are permission requirements, or what happens on error. The description is minimal 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose ('Draw a line on the canvas'), followed by a structured Args section. Every sentence earns its place with no wasted words, making it efficient and easy to scan.

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?

Given 7 parameters with 0% schema coverage and no annotations or output schema, the description is minimally complete. It covers the basic action and parameters but lacks context on file handling, error behavior, or output, which is a gap for a mutation tool with many parameters.

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 description coverage is 0%, but the description compensates by listing all 7 parameters with brief semantics (e.g., 'Starting x coordinate', 'Hex color code'). It adds meaning beyond the schema's bare titles, though details like coordinate ranges or color format specifics are still missing.

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 the specific action ('Draw a line') and resource ('on the canvas'), with the Aseprite context implied. It distinguishes from siblings like draw_circle, draw_rectangle, and draw_pixels by specifying line drawing specifically.

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_pixels or fill_area. The description doesn't mention prerequisites (e.g., needing an existing Aseprite file) or contextual constraints, leaving usage unclear beyond the basic action.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ext-sakamoro/AsepriteMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server