Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

set_onion_skin

Idempotent

Configure Aseprite onion-skin settings: toggle the view, set previous and next ghost frame counts, and keep ghosts within the current tag.

Instructions

Configure the editor's onion-skin view: on/off, ghost counts each direction, and whether ghosting stays inside the current tag. A view preference — visually meaningful in the live editor. (For a rendered onion-skin image any backend can produce, use render_onion_composite.)

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": {
      "active": "<active>"
    },
    "name": "set_onion_skin"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
activeYes
loop_tagNo
next_framesNo
prev_framesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations only supply idempotentHint=true, so the description carries most of the burden. It usefully discloses that this is a view preference affecting the live editor only, not rendered output, but says nothing about whether the setting persists across sessions, whether the backend must be connected, or what happens to unset fields (defaults are 1 for ghost counts).

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?

Two compact sentences with the configuration scope front-loaded and the sibling routing in a clean parenthetical. Nothing is wasted and the em-dash clause about the live editor adds genuine meaning about the tool's effect.

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 five-parameter mutation with no output schema and no annotation coverage beyond idempotency, the description covers purpose, effect, parameter meaning, and the key alternative. The main remaining gap is the unexplained 'file' parameter and any note on persistence or required editor state.

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?

With 0% schema description coverage the description must supply the meaning, and it maps most parameters: on/off to 'active', 'ghost counts each direction' to next_frames/prev_frames, and 'whether ghosting stays inside the current tag' to loop_tag. However, the 'file' parameter is never explained, and it doesn't disambiguate which count is forward versus backward or note the defaults.

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 ('Configure the editor's onion-skin view') and enumerates the settings it controls: on/off, ghost counts per direction, and tag-scoped ghosting. It explicitly distinguishes itself from the sibling render_onion_composite, so an agent can tell the two apart without opening either schema.

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?

Names the alternative render_onion_composite along with the condition that selects it ('for a rendered onion-skin image any backend can produce'). It also frames the tool as a live-editor view preference, which implicitly tells the agent to use it when changing what the editor displays rather than producing output; explicit when-not guidance is absent but the routing is clear.

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