Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

batch_export

Export every .aseprite file in a folder to images, optionally upscaling the first frame by an integer scale; write results to a chosen output directory without changing source files.

Instructions

Export every .aseprite in folder (first frame) to an image, optionally integer-upscaled by scale. Non-destructive: writes <name>.<format> to out_dir (default = folder); never modifies the source. Continues past per-file errors. Headless. (file is ignored — this operates on a folder.)

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": {
      "folder": "<folder>"
    },
    "name": "batch_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
scaleNo
folderYes
formatNopng
out_dirNo
recursiveNo

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?

With only a title annotation and no readOnly/destructive hints, the description carries the burden and does well: it declares the operation non-destructive, says sources are never modified, specifies writes to '<name>.<format>' in out_dir, and discloses that per-file errors do not abort the run. It does not say what the response contains or how failures are reported back, which would complete the behavioral picture.

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 definition is dense and front-loaded: the primary action and scope come first, followed by the non-destructive guarantee, output location, and error semantics. Every clause adds information and nothing is padded.

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 six-parameter, no-output-schema batch tool with no safety annotations, it covers nearly everything an agent needs: source scope, output destination, non-destructiveness, iteration semantics, and the ignored parameter. The unexplained 'recursive' flag and the absence of any note on return values are the remaining gaps.

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 description coverage is 0% across six parameters, so the description must compensate and largely does: it explains folder, scale (integer upscale), format, out_dir (with default = folder) and that file is ignored. The 'recursive' parameter is never mentioned, leaving one boolean's behavior entirely undocumented.

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?

The description opens with a specific verb and resource ('Export every .aseprite in folder (first frame) to an image') and immediately scopes it as folder-wide rather than single-file by stating that 'file' is ignored. That contrast with single-file export siblings is explicit enough that an agent can pick this tool without opening 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 Guidelines4/5

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

It clearly establishes the operating context (folder-based, headless, first-frame only, optional integer upscaling) and notes that the 'file' parameter does not apply, which implicitly steers callers away from the single-file export path. It does not name an alternative tool or state explicit when-not-to-use conditions, leaving that inference to the agent.

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