Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

draw_iso_box

Draw a shaded 2:1 isometric box at a pixel coordinate, returning its face polygons so you can attach recessed ports or details in Aseprite.

Instructions

Draw a 2:1 isometric box. The footprint diamond is centered at (center_x, center_y) with the given half_width (full tile width = 2×half_width), rising height px. Top/left/right faces are auto-shaded from color (#rrggbb, light from top-left) with stroke + highlight. Returns the top/SE/SW face corner polygons so you can attach recessed ports or details. 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>",
      "half_width": "<half_width>",
      "height": "<height>",
      "color": "<color>"
    },
    "name": "draw_iso_box"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
colorYes
heightYes
previewNo
center_xYes
center_yYes
half_widthYes

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?

Annotations carry only a title, so the description bears the full burden and does substantial work: auto-shading of top/left/right faces from color with light from top-left, stroke plus highlight, exactly one undo step, returned face polygons, and the headless file requirement. It leaves the meaning of 'file' (input document vs. output path) slightly ambiguous, which keeps it below 5.

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 core action, then geometry, then shading, then returns, then caveats — each sentence adds information. The parenthetical density and stacked conditionals make it read a bit like release notes rather than guidance, but nothing is wasted.

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?

The tool is moderately complex (7 params, mutation with undo) and an output schema exists, so return values needn't be enumerated; the description still sketches face polygons and the preview payload. What remains unspecified is the target canvas/tile when no file is given, a meaningful gap for a drawing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the schema supplies only bare titles, yet the description explains every parameter's meaning: the footprint center, half_width with the explicit 2× relationship to full tile width, height in pixels, color as #rrggbb with a stated light direction, preview's extra return, and file for headless use. This fully compensates for the schema gap.

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 2:1 isometric box') and pins down the geometry (footprint diamond centered at center_x/center_y, half_width, height), which cleanly separates it from draw_iso_cylinder and draw_rectangle. An agent knows exactly what shape this produces without consulting the schema.

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?

Usage is implied by the shape it draws plus two conditional hints ('Headless: pass file', 'preview true also returns...'), and it notes the returned faces let you attach recessed ports or details. However, it never states when to prefer this over draw_iso_cylinder or a flat draw_rectangle, nor any prerequisites beyond the headless case.

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