Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

show_choice_dialog

Displays a non-blocking choice dialog in Aseprite with a message and up to four buttons, then collect the artist's selection via get_dialog_choice.

Instructions

Live editor only: pop a small dialog IN Aseprite with a message and up to 4 option buttons (e.g. approve/redo). Non-blocking — call get_dialog_choice to collect the artist's pick.

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": {
      "message": "<message>",
      "options": "<options>"
    },
    "name": "show_choice_dialog"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoClaude asks
messageYes
optionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the thin annotation set (only openWorldHint) by disclosing that the call is non-blocking, that the dialog renders inside Aseprite, and that options are capped at 4 — a real constraint absent from the schema, which places no maxItems on the array. It stops short of saying what the immediate return value is or whether dialogs stack when called repeatedly.

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 sentences, no filler, with the environment restriction front-loaded before the behavior and the follow-up call. Every clause carries information an agent needs.

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?

With no output schema, the description correctly preempts the obvious confusion by telling the agent that the choice is not returned here but via get_dialog_choice. The only shortfall is the unexplained title parameter and no note on what happens if options exceeds 4.

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

Parameters3/5

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

Schema description coverage is 0% and the options array has an empty item type, so the description's 'up to 4 option buttons (e.g. approve/redo)' usefully implies a bounded list of strings. However, the 'title' parameter (default 'Claude asks') is never explained, and the required 'message' is only implied.

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 (pop a dialog in Aseprite) plus the payload (a message and up to 4 option buttons). It also scopes the tool ('Live editor only') and names the companion tool that retrieves the answer, so it is distinguishable from get_dialog_choice 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 Guidelines5/5

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

'Live editor only' is an explicit when-not condition that rules out headless/batch contexts. It also states the required follow-up ('call get_dialog_choice to collect the artist's pick'), which is the alternative an agent would otherwise confuse with this tool.

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