Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

set_cel_opacity

Idempotent

Set a cel's opacity from 0 to 255 to control transparency in Aseprite, with optional file, frame, and layer targeting.

Instructions

Set the cel's opacity (0-255).

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": {
      "opacity": "<opacity>"
    },
    "name": "set_cel_opacity"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
frameNo
layerNo
opacityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations only declare idempotentHint=true, so the description should carry more of the behavioral burden. It does disclose the valid value range (0-255), which is real added value, but says nothing about which cel is targeted when file/frame/layer are omitted, or what happens on an invalid target.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence that is front-loaded and waste-free, but its brevity stems from under-specification rather than discipline given four undocumented parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four parameters at 0% coverage, no output schema, and minimal annotations, the description is not complete enough for reliable invocation. It should at least explain how file/frame/layer identify the target cel and the default targeting behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters. The description only clarifies the opacity range; the file, frame, and layer parameters that select the target cel are completely unexplained in both schema and description, leaving the agent to guess their semantics.

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 resource: sets a cel's opacity on a 0-255 scale. An agent can tell it mutates cel transparency, but the description never distinguishes it from siblings like tween_cel_opacity (animated) or set_layer_opacity (different target).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus tween_cel_opacity or set_layer_opacity, and no prerequisites such as needing an active sprite or target cel. The agent must infer usage entirely.

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