Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

get_dialog_choice

Read-only

Poll a choice dialog opened by show_choice_dialog; returns done=false while it remains open, then the chosen button text.

Instructions

Poll the result of show_choice_dialog: done false while the dialog is open, then the chosen button text.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_dialog_choice"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 already declare readOnlyHint=true, and the description is consistent with that. It adds real behavioral detail beyond the annotations — the 'done' flag semantics and the fact that the final value is the chosen button text — but says nothing about polling frequency, timeouts, or behavior if no dialog was ever opened.

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?

A single sentence with no filler, front-loading the action and then the return-value contract. Every clause carries information.

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 and no parameters, the description rightly spends its words on the return contract (done flag, chosen button text) rather than on inputs. It leaves minor gaps around polling cadence and the no-dialog case, but is otherwise complete for a trivial poll tool.

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?

The tool takes zero parameters, so the schema alone is sufficient and the description has no parameter meaning to add; baseline applies.

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 — 'Poll the result of show_choice_dialog' — and names the companion tool that creates the state being read, so an agent can immediately tell this apart from show_choice_dialog itself.

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?

The pairing with show_choice_dialog implies the usage context (call this after opening the dialog), and 'done false while the dialog is open' tells the agent to keep polling. It stops short of explicitly stating the call order or what to do on timeout, so it is clear context rather than full when/when-not guidance.

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