Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

draw_polyline

Draw connected line segments through ordered points in Aseprite, optionally close the shape, and preview the before/after result with changed-pixel stats.

Instructions

Stroke connected line segments through points (ordered [x, y] pairs); close=True joins the last point back to the first. 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": {
      "points": "<points>",
      "color": "<color>"
    },
    "name": "draw_polyline"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
closeNo
colorYes
pointsYes
previewNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

With annotations carrying only a title, the description does real work: it discloses that the operation consumes exactly one undo step, that headless contexts require the file parameter, and that preview yields a before/after canvas picture with changed-pixel count and bbox. It does not say which layer/tile receives the stroke or what happens when file is omitted in headless mode, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with no filler: geometry and close semantics first, then the mutate/headless/preview notes. Every clause conveys distinct, actionable 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?

For a five-parameter drawing tool with an output schema available, the description covers geometry, undo cost, headless requirements, and preview side effects, which is most of what an agent needs. The remaining gap is color value format and the target layer/tile context of the stroke.

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?

Schema description coverage is 0%, so the description must compensate, and it explains four of five parameters meaningfully: points as ordered [x, y] pairs, close joining last to first, file for headless use, and preview returning an extra picture. Only color's expected format (hex, name, or tuple) is left entirely undocumented in both schema and description.

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 description names a specific verb and resource ("Stroke connected line segments through points") and defines the geometry precisely as ordered [x, y] pairs, which distinguishes it from single-segment drawing siblings like draw_line and from shape draws like draw_circle.

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?

It gives an operational prerequisite ("Headless: pass file") but never states when to choose a polyline over the sibling draw_line or a shape tool. Usage is implied by the geometry description rather than stated as guidance 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