Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

relight_scene

Change an Aseprite scene’s time of day to dawn, noon, sunset, or night, shifting colors and optional glows while preserving color count and creating togglable layer copies.

Instructions

Show a scene at another time of day: dawn, noon, sunset, or night. Each colour's lightness, warmth, and saturation shift the way that light would, and each maps to one new colour, so the colour count stays the same. glows are lanterns or windows, [[x, y, radius], ...], whose pools stay warm and lit. strength (0-1) blends toward the original. Works on layers (every visible image layer by default), writing a copy named like "Ground (night)" above each and hiding the original, so switching back is a visibility toggle. One undo step. Headless: pass file.

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": {
      "time": "<time>"
    },
    "name": "relight_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
timeYes
glowsNo
layersNo
strengthNo
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 full burden and does so well: it discloses that a copy named like "Ground (night)" is written above each layer, the original is hidden, the operation is one undo step, and the color count is preserved. The notable gap is the undocumented 'all_frames' default of true, so an agent cannot tell that frame-based scenes are relit across all frames.

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?

Purpose is front-loaded, then parameters and side effects, then the headless escape hatch. Every sentence conveys information an agent needs; there is no restatement of the name or filler.

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 six-parameter mutation tool with no annotations and no output schema, the description covers almost everything an agent needs, including side effects, undo cost, and parameter formats. It falls short only on the undocumented 'all_frames' flag and on validation behavior for an invalid 'time' string.

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 does: it supplies the four valid 'time' values, the glow tuple format [[x, y, radius]] and their meaning, the 0-1 blend semantics of 'strength', the layer default, and the 'file' headless mode. Only 'all_frames' is left entirely undefined, which is the one meaningful omission.

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 ('Show a scene at another time of day') and enumerates the exact allowed modes (dawn, noon, sunset, night). This clearly separates it from sibling color tools like adjust_hsl or adjust_brightness_contrast, which alter colors without the time-of-day mapping.

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 operating context: it acts on visible image layers by default, on a specified layer set otherwise, and offers a 'headless: pass file' path. It also notes that reverting is a visibility toggle rather than an undo, which implies when this is safe to use. It does not name explicit alternatives or state when not to use it.

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