Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

draw_line

Draws a 1px line between two coordinates as a single undoable edit, with optional headless file targeting and a preview showing changed pixels and bounding box.

Instructions

Draw a 1px line from (x1,y1) to (x2,y2). 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": {
      "x1": "<x1>",
      "y1": "<y1>",
      "x2": "<x2>",
      "y2": "<y2>",
      "color": "<color>"
    },
    "name": "draw_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1Yes
x2Yes
y1Yes
y2Yes
fileNo
colorYes
previewNo

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 full burden and does well: it discloses 1px stroke width, that the operation is grouped into "one undo step" (mutation with known undo granularity), the headless file requirement, and what preview adds (before/after image, changed-pixel count, bbox). Missing is what happens to coordinates outside the canvas and whether color replaces or blends.

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?

Front-loaded with the core action, then two compact clauses for the conditional behaviors. No filler, and the telegraphic style ("Headless: pass ``file``") stays unambiguous.

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?

The output schema means return values need not be spelled out, and the mutation/undo semantics are covered. However, for a 7-parameter tool with zero schema descriptions and no safety annotations, the undocumented required `color` argument and unstated out-of-bounds behavior leave real gaps.

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. It gives meaning to x1/y1/x2/y2 (endpoints), file (headless target), and preview (before/after picture), but leaves the required `color` parameter entirely undefined — no format, no hint whether hex, name, or index applies.

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 concrete verb and resource with exact geometry: "Draw a 1px line from (x1,y1) to (x2,y2)". It is distinguishable from drawing siblings on name alone, but the description never names an alternative (e.g. draw_polyline for multi-segment) to sharpen the boundary.

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?

Implied context is present: "Headless: pass ``file``" tells the agent the condition for supplying a file, and "preview true also returns..." tells it when extra output is produced. There is no when-not guidance and no comparison to sibling draw tools, so an agent must infer which one to pick.

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