Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

iso_recessed_panel

Draws a recessed docking socket or I/O port on an isometric face from four corner points, with a lit lip framing a dark recess. Applies a consistent I/O-port style in one undo step.

Instructions

Draw a recessed docking socket/port on an isometric face — a light lit lip framing a dark recessed interior. points = the 4 corner [x, y] pairs of a face (e.g. the face_se returned by draw_iso_box). This is the consistent I/O-port style. 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>"
    },
    "name": "iso_recessed_panel"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
pointsYes
previewNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/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 disclose key behavior: the operation is a single undoable step ('One undo step'), it writes to a file in headless mode, and with preview it returns a before/after canvas image plus changed-pixel count and bbox. It does not state which layer/target is modified or any constraints on the supplied points (e.g. planarity or ordering).

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?

The visual description is front-loaded and the supporting details (points source, undo, headless, preview) follow in a compact second block. Wording is efficient with no filler, though the preview sentence is appended rather than integrated into the main flow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 need no further explanation, and the description still supplements it for the preview mode. For a three-parameter drawing tool with minimal annotations, it supplies the visual target, the input source, undo behavior, and headless handling — everything needed to call it correctly.

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%, and the description compensates for all three parameters: points is defined as the four corner [x, y] pairs of a face, file is tied to headless operation, and preview is explained in terms of what extra output it returns. The file parameter's exact semantics (path vs handle) remains slightly vague, keeping it below a 5.

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?

The description opens with a specific verb and resource ('Draw a recessed docking socket/port on an isometric face') and adds a concrete visual definition ('light lit lip framing a dark recessed interior'), which separates it from structural siblings like draw_iso_box or draw_iso_cylinder. It does not explicitly contrast itself with the other decorative add_*/draw_* tools, so it stops short of full sibling differentiation.

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?

It tells the agent where the required input comes from (the four corner points of a face, e.g. face_se from draw_iso_box) and notes the environment switch 'Headless: pass file'. 'This is the consistent I/O-port style' implies when this variant is the right choice. There is no explicit when-not guidance or named alternative for other port looks.

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