Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

set_layer_opacity

Idempotent

Adjust a layer's opacity (0-255) in Aseprite to control transparency for pixel-art edits, animations, and exports.

Instructions

Set a layer'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": {
      "name": "<name>",
      "opacity": "<opacity>"
    },
    "name": "set_layer_opacity"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
nameYes
opacityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations only declare idempotentHint, so the description must carry the rest. It does not state that this is a mutating operation on the document, whether the change is undoable, or what happens if the layer name does not match. Only the range constraint is disclosed.

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?

A single short sentence with no filler and the key constraint (0-255) placed inline. It is terse to the point of under-specification, but nothing is wasted.

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?

For a mutating three-parameter tool with no output schema and zero schema descriptions, the definition leaves the `file` targeting behavior and layer-name matching unspecified. An agent could call it correctly only by guessing at those parameters.

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 three parameters. The description clarifies the opacity range, but says nothing about `name` (presumably the layer identifier, case sensitivity, duplicates) or `file` (which document is targeted when null). It compensates for only one of three parameters.

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 ("Set a layer's opacity") and adds the valid range 0-255, which distinguishes it from sibling set_cel_opacity at the resource level. It stops short of explicitly contrasting with the cel variant, so sibling differentiation is only implicit.

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 indication of when to use this versus set_cel_opacity, set_layer_blend_mode, or tween_cel_opacity, and no note about prerequisites (layer must exist, sprite must be selected). The only usage-adjacent content is the numeric range.

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