Skip to main content
Glama

draw_ellipse

Draw an ellipse or circle on an Aseprite sprite by specifying center coordinates and radii, with options for filled or outlined shapes and antialiasing.

Instructions

Draw an ellipse centred at (center_x, center_y) with the given radii.

For a circle, use the same value for radius_x and radius_y. filled=False draws a 1px outline, and a filled ellipse is exactly that outline with its interior: the two are one shape rendered two ways, so a fill and an outline of the same call line up. antialias smooths a filled ellipse with sub-pixel coverage (RGB sprites only; ignored otherwise).

Coordinates: (0, 0) is the top-left pixel. x grows right, y grows DOWN. A span given as position plus size covers x .. x + width - 1, so width is a count of pixels, not an offset to the far edge.

Centring differs between primitives, so check this when aligning two shapes:

  • draw_rectangle(x, width) spans x .. x+width-1, centred on x + (width-1)/2. An even width therefore centres on a half pixel.

  • draw_ellipse(center, radius) spans center-radius .. center+radius, which is always an ODD 2*radius+1 pixels wide and always centred on a whole pixel.

  • draw_ellipse_in_box(x, y, width, height) takes the same bounding box as draw_rectangle and fills it exactly, so it is the one to use for an even diameter, a disc centred on an even canvas, or a circle that has to line up with a rectangle.

  • draw_symmetric_pixels mirrors about the canvas, not about either of the above.

Writes falling outside the canvas are dropped rather than raising. Every drawing tool reports pixels_written, and pixels_clipped when anything was dropped, so compare those against what you asked for rather than trusting ok.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorYes
frameNoDefault: 1.
layerNo
filledNoDefault: false.
center_xYes
center_yYes
filenameYes
radius_xYes
radius_yYes
antialiasNoDefault: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changedv0.10.0
    • addedInput schema / properties / antialias / description
      Added value: +"Default: false."
    • removedInput schema / properties / antialias / title
      Removed value: -"Antialias"
    • removedInput schema / properties / center_x / title
      Removed value: -"Center X"
    • removedInput schema / properties / center_y / title
      Removed value: -"Center Y"
    • removedInput schema / properties / color / title
      Removed value: -"Color"
    • removedInput schema / properties / filename / title
      Removed value: -"Filename"
    • addedInput schema / properties / filled / description
      Added value: +"Default: false."
    • removedInput schema / properties / filled / title
      Removed value: -"Filled"
    • addedInput schema / properties / frame / description
      Added value: +"Default: 1."
    • removedInput schema / properties / frame / title
      Removed value: -"Frame"
    • removedInput schema / properties / layer / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / layer / default
      Removed value: -null
    • removedInput schema / properties / layer / title
      Removed value: -"Layer"
    • addedInput schema / properties / layer / type
      Added value: +"string"
    • removedInput schema / properties / radius_x / title
      Removed value: -"Radius X"
    • removedInput schema / properties / radius_y / title
      Removed value: -"Radius Y"
    • removedInput schema / title
      Removed value: -"draw_ellipseArguments"
  2. First observedv0.7.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only mark this as a non-read-only, closed-world write. The description adds real behavioral context: filled=False gives a 1px outline that lines up exactly with the filled version, antialias applies only to filled RGB sprites, out-of-canvas writes are dropped rather than raising, and pixels_written/pixels_clipped should be compared against intent instead of trusting ok.

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?

Purpose and the fill/antialias semantics are front-loaded, and the coordinate and centring details are grouped into scannable bullets. It is somewhat long for a single drawing primitive, but nearly every line carries non-obvious information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description covers the coordinate system, clipping behavior, and the keys returned (pixels_written, pixels_clipped), so return-shape handling is addressed. The main omission is format/meaning for color, layer, and frame, which a caller still has to infer.

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 coverage is only 30%, so the description must compensate. It gives strong meaning for center, radius, filled, and antialias (odd 2*radius+1 span, whole-pixel centring, fill/outline equivalence), but leaves color, layer, frame, and filename entirely unexplained - roughly half the parameters remain undocumented in either place.

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 first sentence states a specific verb and resource with the exact anchoring parameters (center_x, center_y, radii). It also distinguishes this primitive from draw_ellipse_in_box, draw_rectangle, and draw_symmetric_pixels via the centring bullet list, so an agent can select it without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing guidance: use this for a circle (radius_x == radius_y) and for pixel-centred spans, and switch to draw_ellipse_in_box for even diameters, discs on even canvases, or circles that must align with a rectangle. The when-to-use-vs-sibling condition is spelled out.

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