Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

set_layer_visibility

Idempotent

Toggle a named layer's visibility in an Aseprite file to show or hide it during pixel-art editing or animation.

Instructions

Show or hide a layer.

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>",
      "visible": "<visible>"
    },
    "name": "set_layer_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
nameYes
visibleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations only declare idempotentHint=true, leaving the mutation profile and side effects undisclosed. The description does not say what happens if the named layer does not exist, whether the file parameter falls back to the active document, or whether hiding affects rendering/export.

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?

The single sentence is front-loaded and contains no filler, so it is structurally sound. However, its brevity reflects under-specification rather than efficiency, since essential calling context is absent.

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 three-parameter mutation tool with no output schema and only an idempotency hint, the description should carry the behavioral burden. It omits file resolution, missing-layer behavior, and return information, leaving the agent to guess at call correctness.

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 word "layer" vaguely maps to the name parameter and "show or hide" maps to visible, but the file parameter (defaulting to null) is given no meaning, and name-matching semantics (exact, path-qualified, case sensitivity) are unstated.

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?

The description gives a clear verb pair ("Show or hide") and a specific resource ("a layer"), which cleanly separates it from siblings like set_layer_opacity or set_layer_blend_mode that modify other layer attributes. It does not explicitly name a sibling it is not, 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 Guidelines2/5

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

There is no guidance on when to use this versus rename_layer, select_layer, or delete_layer, and no prerequisites or exclusions are stated. The only implied usage is the tautological 'to change visibility,' which an agent could infer from the name alone.

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