Skip to main content
Glama
ext-sakamoro

Aseprite MCP Tools

by ext-sakamoro

draw_circle

Draw circles on Aseprite canvas by specifying center coordinates, radius, color, and fill options for pixel art creation.

Instructions

Draw a circle on the canvas.

Args: filename: Name of the Aseprite file to modify center_x: X coordinate of circle center center_y: Y coordinate of circle center radius: Radius of the circle in pixels color: Hex color code (default: "#000000") fill: Whether to fill the circle (default: False)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
center_xYes
center_yYes
radiusYes
colorNo#000000
fillNo

Implementation Reference

  • The `draw_circle` function acts as the MCP tool handler, validating inputs and invoking the `LuaBuilder` to generate and execute the Lua script for Aseprite.
    async def draw_circle(filename: str, center_x: int, center_y: int, radius: int, color: str = "#000000", fill: bool = False) -> str:
        """Draw a circle on the canvas.
    
        Args:
            filename: Name of the Aseprite file to modify
            center_x: X coordinate of circle center
            center_y: Y coordinate of circle center
            radius: Radius of the circle in pixels
            color: Hex color code (default: "#000000")
            fill: Whether to fill the circle (default: False)
        """
        try:
            # Validate inputs
            file_path = validate_file_path(filename, must_exist=True)
            color = validate_color(color)
            
            if radius < 1:
                raise ValidationError("radius", radius, "Radius 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_circle(center_x, center_y, radius, color, fill)
            builder.end_transaction()
            builder.save_sprite()
            
            # Execute script
            cmd = get_command()
            success, output = cmd.execute_lua_script(builder.build(), str(file_path))
            
            return f"Circle drawn successfully in {file_path}"
            
        except (ValidationError, AsepriteError) as e:
            return f"Failed to draw circle: {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?

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool modifies a file ('modify'), implying mutation, but doesn't disclose permissions needed, whether changes are destructive/reversible, error conditions, or what happens if the file doesn't exist. The description adds minimal behavioral context 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?

The description is appropriately sized and front-loaded with the main purpose in the first sentence. The parameter explanations are organized but could be more concise; some details like 'default' values are redundant with the schema.

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?

For a mutation tool with 6 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks behavioral details (e.g., error handling, side effects), usage context, and doesn't fully compensate for the missing parameter documentation, making it inadequate for safe and effective use.

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 0%, so the description must compensate. It provides parameter names and basic semantics (e.g., 'X coordinate of circle center', 'Radius in pixels', 'Hex color code'), adding meaningful context beyond schema titles. However, it doesn't explain constraints like valid coordinate ranges or color format specifics, leaving some gaps.

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 the action ('Draw a circle') and target ('on the canvas'), specifying the resource being modified. It distinguishes from siblings like 'draw_line' or 'draw_rectangle' by specifying the shape, but doesn't explicitly differentiate from other drawing tools in terms of when to choose one over another.

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 provided on when to use this tool versus alternatives like 'draw_rectangle' or 'draw_line'. The description mentions modifying an Aseprite file but doesn't specify prerequisites, context, or exclusions for usage.

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