Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

make_normal_map

Generate a normal map from Aseprite layers or visible art so 2D sprites react to moving lights in Godot and Unity, with adjustable bevel, detail, and strength.

Instructions

Make a normal map so the art reacts to 2D lights in Godot and Unity: a torch moving past shades it. Forms round off over bevel pixels from their outline, detail (0-1) lets bright areas stand forward, and strength steepens it all. It goes on a hidden "Normal map" layer, and save_path also writes it as a PNG strip matching an exported sprite sheet (frames side by side). In Godot, set it as the normal map of a CanvasTexture whose diffuse is the sprite; in Unity, add it to the sprite's Secondary Textures as _NormalMap. Made from layer, or everything visible by default. One undo step. Headless: pass file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "make_normal_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
bevelNo
layerNo
detailNo
strengthNo
save_pathNo
all_framesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

With only a title annotation, the description carries the burden and does well: it discloses the output destination (a hidden 'Normal map' layer), the PNG-strip side effect of save_path matching an exported sprite sheet, and 'One undo step'. Not covered: whether an existing normal map layer is replaced, or cost on large sprite sheets.

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 purpose and effect before engine-specific instructions; every sentence carries information about parameters or integration. It is dense but justified by seven undocumented parameters, though the Godot/Unity setup sentences could be tightened.

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?

For a 7-parameter, no-annotation, no-output-schema tool, the description covers effect, source selection, tunables, output location, side effects, undo behavior, and headless mode. The only real gap is the undefined 'all_frames' flag, which is minor relative to what is supplied.

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 coverage is 0%, so the description must compensate, and it explains six of seven parameters with real meaning: bevel (rounding distance from the outline), detail (0-1, bright areas stand forward), strength (steepens), layer (source), save_path (PNG strip), file (headless input). 'all_frames' is only obliquely implied by 'frames side by side' and is never defined.

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 ('Make a normal map') and immediately gives the observable outcome ('the art reacts to 2D lights... a torch moving past shades it'). No sibling tool does normal-map generation, and the description makes that scope unmistakable.

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?

Clear context for when to reach for it (2D lighting in Godot/Unity) plus concrete integration steps: CanvasTexture normal map in Godot, Secondary Textures '_NormalMap' in Unity, and 'Headless: pass ``file``'. It does not name alternatives or when-not-to-use cases, so it falls 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