Skip to main content
Glama

draw_circle

Draw a circle on an Aseprite canvas at specified center coordinates and radius, with optional color and fill.

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
fillNo
colorNo#000000
radiusYes
center_xYes
center_yYes
filenameYes
Behavior2/5

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

With no annotations, the description carries the full burden. It mentions drawing a circle but does not disclose whether it overwrites existing content, blends, or creates new layers. The side effects (e.g., modifying the file) are implicit but not explicit.

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 concise: one sentence plus a parameter list. It is well-structured and avoids unnecessary words, though the parameter list could be integrated more naturally.

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 complexity of drawing tools among siblings, the description is minimal. It does not mention the current layer or frame context, nor does it describe the return value or success conditions. The default values for color and fill are provided, but more context would be helpful.

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 description provides meaningful explanations for each parameter (e.g., 'center_x: X coordinate of circle center'), which the input schema lacks (schema coverage 0%). This adds value beyond the schema properties that only have titles.

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 that the tool draws a circle on the canvas, specifying the verb and resource. However, it does not differentiate from sibling tools like draw_circle_at, which likely has a similar purpose.

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 (e.g., draw_ellipse_at, draw_rectangle). There is no mention of prerequisites or context such as current layer or frame.

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/NosytLabs/aseprite-mcp'

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