Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

draw_iso_cylinder

Draw vertical isometric cylinders, tanks, silos, or chimneys with an auto-shaded body, top ellipse, and front rim from a chosen color, with optional headless file preview.

Instructions

Draw a vertical isometric cylinder (tank/silo/chimney): top ellipse + shaded body + front rim, auto-shaded from color. top_y is the top of the body. 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>",
      "top_y": "<top_y>",
      "radius": "<radius>",
      "height": "<height>",
      "color": "<color>"
    },
    "name": "draw_iso_cylinder"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
colorYes
top_yYes
heightYes
radiusYes
previewNo
center_xYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/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 must do the behavioral work — and it does: it discloses automatic shading derived from the color argument, that the operation is a single undo step (directly relevant given the 'undo' sibling), the headless file-output mode, and what preview additionally returns (before/after image, changed-pixel count, bbox). It leaves gaps on overlap behavior, coordinate units, and color format, so it is not fully transparent.

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?

Front-loaded with the drawing result, then parameter semantics, then mode/return notes — no filler sentences. It is written as terse fragments with doubled backticks that read slightly awkwardly, but nothing is redundant.

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 7-parameter mutation tool with no behavioral annotations, the description covers the operation, the undo footprint, headless output, and the preview return path; an output schema exists so return values need not be re-explained. Missing details about coordinate units, color format, and behavior when overwriting existing pixels are the only remaining gaps.

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 does for the non-obvious parameters: top_y is pinned down as 'the top of the body' (not the top of the ellipse), color is identified as the shading source, file as the headless target, and preview as the before/after report flag. center_x, radius, and height are left to name inference with no units or coordinate-system note, which keeps it out of 5 territory.

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?

States a specific verb and resource ('Draw a vertical isometric cylinder') and immediately decomposes what that means visually (top ellipse + shaded body + front rim) plus concrete subject examples (tank/silo/chimney). An agent can distinguish this from draw_iso_box or draw_circle purely from the text.

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

Usage Guidelines4/5

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

Gives clear usage context: 'vertical' constrains orientation, 'auto-shaded from color' tells the agent no separate shading pass is needed, 'Headless: pass file' covers the non-interactive mode, and preview covers the inspect-after-draw path. It never explicitly says when to prefer a sibling (e.g., box vs cylinder) or what it excludes, so it stops short of a 5.

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