Skip to main content
Glama
Sign In
Aseprite MCP Tools

Aseprite MCP Tools

by NosytLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

draw_circle_at

Draw a circle with specified center, radius, color, and optional fill on a chosen layer and frame in an Aseprite file. Automatically creates the layer if needed.

Instructions

Draw a circle on a specific layer/frame.

Args: filename (str): The path to the Aseprite file. layer_name (str): The name of the layer to draw on. frame_index (int): The index of the frame to draw on. center_x (int): The x coordinate of the center of the circle. center_y (int): The y coordinate of the center of the circle. radius (int): The radius of the circle. color (str, optional): The color to draw the circle with. Defaults to "#000000". fill (bool, optional): Whether to fill the circle. Defaults to False. create_if_missing (bool, optional): Whether to create the layer if it doesn't exist. Defaults to True.

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": {
      "filename": "<filename>",
      "layer_name": "<layer_name>",
      "frame_index": "<frame_index>",
      "center_x": "<center_x>",
      "center_y": "<center_y>",
      "radius": "<radius>"
    },
    "name": "draw_circle_at"
  }
}

Input Schema

NameRequiredDescriptionDefault
fillNo
colorNo#000000
radiusYes
center_xYes
center_yYes
filenameYes
layer_nameYes
frame_indexYes
create_if_missingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so the description must fully disclose behavior. It does not state if the operation is destructive, requires file saving, or what happens on failure. For a drawing tool, key details like whether existing content is overwritten or merged are missing.

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 relatively concise with a clear one-line purpose followed by a parameter list. The front-loading is effective. However, the docstring format with 'Args' is slightly verbose but acceptable.

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 the tool has 9 parameters and no output schema, the description adequately explains each parameter's role. However, it lacks details on return values, side effects, or behavior when layer/frame is missing. For a drawing command, completeness is moderate.

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?

The description provides basic explanations for each parameter (e.g., 'The x coordinate of the center'), which adds meaning beyond the schema's titles. However, the schema has 0% description coverage, so these are essential. The explanations are minimal and don't cover nuances like color format or coordinate system.

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 it draws a circle on a specific layer/frame. However, it does not differentiate from the sibling tool 'draw_circle', which likely has a similar function without specifying layer/frame, limiting clarity for selection.

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_circle' or 'draw_ellipse_at'. No mention of prerequisites, when not to use, or constraints such as whether the layer must exist (only the parameter 'create_if_missing' hints at it).

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