Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

paint_sky

Generates a layered sky background for pixel art, with selectable time of day, dithered bands, clouds, sun or moon glow, stars, and optional looping cloud drift.

Instructions

Paint a sky behind the art: dawn, day, sunset, or night, shaded in dithered bands from the top down to row horizon (the bottom edge by default). sun is [x, y] for the sun or moon: the sky glows round it and the clouds are lit from its side. clouds is how much they cover (0-1, 0 for none) and stars how many show (0-1; each time has its own default). seed changes the cloud shapes. drift is how many pixels the clouds travel over the sprite's frames (negative for leftward; try 1 per frame): they then go on their own "Clouds" layer and loop seamlessly. The sky goes on a new layer named layer at the bottom of the stack, on every frame. Follow with paint_mountains and reflect_in_water for a lake. 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": "paint_sky"
  }
}

Input Schema

NameRequiredDescriptionDefault
sunNo
fileNo
seedNo
timeNosunset
driftNo
layerNoSky
starsNo
cloudsNo
horizonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations carry only a title, so the description bears the whole burden and does well: it discloses that the sky lands on a new named layer at the bottom of the stack on every frame, that drifting clouds move to their own 'Clouds' layer and loop seamlessly, that the operation is a single undo step, and that headless use requires `file`. These are exactly the side effects an agent needs before invoking a mutation.

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, then parameter semantics, then workflow and side effects. Nearly every clause adds information, though the dense run-on parentheticals (e.g. the horizon default and the drift aside) could be split for faster scanning.

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 9-parameter mutation with no output schema and minimal annotations, the definition covers purpose, every parameter, side effects, and the follow-on workflow. The only gap is that it never hints at what the call returns or what happens on name collisions, which matters slightly more here because no output schema exists.

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%, so the description must carry parameter meaning and it does for essentially every argument: horizon as a row with default bottom edge, sun as [x, y] with glow and cloud lighting, clouds as 0-1 coverage, stars as 0-1 with per-time defaults, seed for cloud shape, drift in pixels with sign convention, and the destination layer name. That is well beyond what the bare schema types convey.

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 concrete verb and resource ('Paint a sky behind the art') and immediately enumerates the four supported presets (dawn, day, sunset, night), so an agent knows exactly what the tool produces. It also names the natural follow-up siblings (paint_mountains, reflect_in_water), which situates it in a workflow rather than leaving it ambiguous.

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 actionable context: 'Follow with paint_mountains and reflect_in_water for a lake' and 'try 1 per frame' for drift. It does not state when not to use it, nor what happens if a layer named `layer` already exists, so it stops short of full routing guidance.

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