Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

add_glow

Adds a dithered light pool on a new layer to simulate fire, lantern, or window glow, with adjustable color, radius, strength, and flicker animation.

Instructions

Light the scene from a fire, lantern, or window at x, y: a pool of color that fades out by radius in dithered steps, on a new layer that adds its light to what is under it. strength is 0-1. flicker (0-1) makes the pool breathe as a seamless loop over every frame. on_layers are the top-level layers the light lands on (the ground, a figure); open air round them takes only air of it, so the sky behind a campfire stays dark. By default it lights everything. The layer is named layer and goes on top. 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": {
      "x": "<x>",
      "y": "<y>",
      "radius": "<radius>"
    },
    "name": "add_glow"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
airNo
fileNo
colorNo#ff8c3c
layerNoGlow
radiusYes
flickerNo
strengthNo
on_layersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations supply only a title, so the description carries the behavioral burden and does it well: it discloses that a new layer is created on top, that the light is additive over what is under it, that it is one undo step, and that headless mode requires passing ``file``. It leaves the return value and whether existing layers are touched unstated, so not a 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?

Dense but well organized: purpose first, then per-parameter semantics, then layer/undo/headless behavior. Some clauses are winding ("open air round them takes only air of it, so the sky behind a campfire stays dark"), but every sentence adds usable information.

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 10-parameter effect tool with no output schema and only a title annotation, the description covers parameters, layer side effects, undo cost, and headless invocation. The one gap is the return value, which no output schema documents either.

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% and all ten parameters are bare names, yet the description explains almost all of them: ``strength`` is 0-1, ``flicker`` is 0-1 and loops seamlessly, ``on_layers`` scopes which layers receive light, ``air`` is the fraction that lands on open air, plus ``color``, ``radius``, ``layer``, and ``file``. It omits coordinate units and the ``air`` default/range, keeping it from 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?

States a specific verb and effect: "Light the scene from a fire, lantern, or window at x, y: a pool of color that fades out by radius in dithered steps, on a new layer." An agent immediately knows this paints a light pool rather than a rim light or mist. It does not name a sibling alternative, so it stops short of a 5.

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 described effect (fire, lantern, or window lighting), but there is no explicit when-to-use, when-not-to-use, or "use add_rim_light instead for X" guidance. The agent must infer the choice from the effect described.

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