Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

close_sprite

Destructive

Close the active sprite to free its editor tab. Errors on unsaved changes unless force=true is passed, so save first or discard deliberately.

Instructions

Close the active sprite. Errors if it has unsaved changes unless force=true — save_sprite first, or force to discard them. Aimed at the live editor (frees the tab); headless has no persistent session, so there is nothing to close there.

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

Input Schema

NameRequiredDescriptionDefault
forceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only flag destructiveHint=true; the description adds the important specifics of what is destroyed (unsaved changes) and under what condition (force=true), plus the failure mode when force is omitted. It does not say whether the close is reversible or what the response contains, so it stops short of full disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the action and the guard condition before the environment caveat. The final sentence about headless is slightly wordy but still earns its place by preventing a wasted call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter tool with no output schema, the description covers the action, the failure condition, the override, the environment caveat, and the alternative. Nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 0%, so the description carries the load for the single `force` parameter, and it does: force=true discards unsaved changes, while the default path errors. It never states the default value or the exact error type, which is why it is not a 5.

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 ("Close the active sprite") with the scope qualifier "active", which separates it cleanly from save_sprite and open_sprite. An agent can identify the operation without consulting the 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?

Names the alternative explicitly ("save_sprite first") and the condition that selects it (unsaved changes), plus an explicit when-not: headless sessions have nothing to close. Both the routing decision and the exclusion are spelled out rather than inferred.

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