Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

draw_circle

Draw a circle or filled disk at a specified center point and radius in Aseprite pixel art, as a single undoable step. Optionally preview before/after changes with pixel count and bounding box.

Instructions

Draw a circle centered at (center_x, center_y). fill true fills the disk. One undo step. Headless: pass file.

preview true also returns a before/after picture of the canvas with the changed-pixel count and bbox.

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": {
      "center_x": "<center_x>",
      "center_y": "<center_y>",
      "radius": "<radius>",
      "color": "<color>"
    },
    "name": "draw_circle"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
fillNo
colorYes
radiusYes
previewNo
center_xYes
center_yYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations carry only a title, so the description bears the weight and does add meaningful behavior: it is a mutating operation consuming 'one undo step', it supports a headless file-backed mode, and preview changes the return payload. It stops short of saying what happens when the circle extends past canvas bounds or what color formats are accepted.

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?

Tight, front-loaded sentences with no filler; the core geometry comes first, then optional behaviors. The reST-style double backticks are slightly noisy but do not impede comprehension.

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?

An output schema exists, so return values needn't be spelled out, and the description usefully notes the extra preview payload (before/after image, changed-pixel count, bbox) that the agent would otherwise have to discover. The remaining gap is parameter-level detail for color and radius, which matters more given 0% schema coverage.

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% across 7 parameters, so the description must compensate, and it explains fill, preview, file, and the center coordinates. It leaves radius and color completely unaddressed (including color format, e.g. hex vs. name) and does not clarify what 'file' is a path to.

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?

States a specific verb and resource ('Draw a circle') and pins the geometry to (center_x, center_y), so the agent knows exactly what operation this performs. It does not explicitly distinguish itself from the sibling draw_ellipse, which is the one nearby tool an agent might confuse it with.

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

Usage Guidelines3/5

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

The 'Headless: pass ``file``' clause gives real situational guidance about a non-default execution mode, but there is no statement of when to prefer draw_circle over draw_ellipse or other primitives, and no preconditions or exclusions.

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