Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

cancel_ask_point

Idempotent

Withdraw a pending ask_point request when the artist has stepped away or you're moving on, releasing the connection and stopping further waiting.

Instructions

Withdraw a pending ask_point request (e.g. the artist stepped away and you're moving on).

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": "cancel_ask_point"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations only supply idempotentHint and a title, so the description carries most of the burden; it does add that the target must be 'pending', which is real behavioral scoping. It says nothing about what happens if the request is no longer pending, whether the artist is notified of the withdrawal, or what the call returns.

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?

The description is one front-loaded sentence, with the actionable verb and object first and the parenthetical motivation as a trailing example. Nothing in it is redundant.

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?

For a zero-parameter state-transition tool with no output schema, the description covers the action, the target state, and a typical motivation. Only the failure/no-op behavior, i.e. what happens when the request is no longer pending, is not covered.

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, and 100% schema coverage applies, so per the rubric the baseline is 4. The description appropriately adds no parameter detail because there is nothing to document.

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 names a specific verb ('Withdraw') and a specific resource ('a pending ask_point request'), and the reference to ask_point plus the 'pending' qualifier separates it from ask_point and get_asked_point. It stops short of explicitly contrasting with those siblings, so a 4 rather than 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 Guidelines3/5

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

A concrete usage scenario is given (the artist stepped away and you're moving on), which implies when to call it. However, no conditions are stated for when not to call it, e.g. once the request has already been answered, and no alternative is named.

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