Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

get_asked_point

Read-only

Polls for the result of an asked canvas point, returning clicked x/y coordinates when ready or a cancelled status if the artist presses Esc.

Instructions

Poll the result of ask_point: done false while waiting, then the clicked x/y (or cancelled if the artist pressed Esc).

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_asked_point"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations only declare readOnlyHint=true, so the description carries the real burden and delivers: it discloses the asynchronous done/pending state machine, the two success outcomes (clicked x/y vs. cancelled via Esc). It omits polling cadence and whether a pending request can expire or be abandoned, which are the remaining behavioral gaps for a poll-style tool.

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?

One sentence, front-loaded with the action and its target, then the outcome states. Every clause carries information an agent needs to interpret the response; nothing is padding.

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 must explain return values and it does (done flag, x/y coordinates, cancelled). For a zero-parameter polling tool this is nearly complete; only timing/expiry behavior and pre-call ordering are left implicit.

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, which is the baseline-4 case. The description correctly signals that no input is needed and puts all its information into result semantics instead.

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?

Names a specific verb and resource ("Poll the result of ask_point") and immediately clarifies the relationship to its sibling ask_point. The stated return shape (done=false, x/y, or cancelled) tells an agent exactly what this tool yields, which differentiates it from ask_point and cancel_ask_point without opening any schema.

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?

"Poll the result of ask_point" establishes the usage context clearly: call this after initiating ask_point, not instead of it. It does not state when to stop polling, expected cadence, or what happens if polled before ask_point is called, so alternatives and exclusions are only partially covered.

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