Skip to main content
Glama
Sign In
Aseprite Asset MCP

Aseprite Asset MCP

by jdsalasca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

animation_workflow_guide

Generate a step-by-step animation workflow for character, environment, or general scenes. Select a use case to receive a concise deterministic guide for Aseprite.

Instructions

Return a concise deterministic guide for character, environment, or general animation workflows.

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

Input Schema

NameRequiredDescriptionDefault
use_caseNocharacter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does add useful traits: the result is 'deterministic' and 'concise,' and 'Return' implies a read-only action. However, it does not describe the response format, error behavior, or any side effects, leaving some uncertainty.

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 a single front-loaded sentence with no filler. Every word earns its place: it states the action, the output nature, and the supported workflow domains.

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

Completeness3/5

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

The tool is low complexity with one optional parameter, but there is no output schema or annotations, so the description is the only behavior source. It provides enough to invoke the tool by choosing among character/environment/general, but it leaves the actual guide contents and exact return representation unspecified.

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 schema's only parameter, use_case, has no description (0% coverage), so the description must compensate. It names the three workflow categories—character, environment, and general—that map to likely input values, giving an agent meaningful guidance beyond the bare schema.

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 uses a specific action ('Return') and a concrete object ('concise deterministic guide'), then scopes it to character, environment, or general animation workflows. This clearly distinguishes the tool from sibling tools that perform direct edits, generation, or inspection.

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 phrase 'for character, environment, or general animation workflows' gives clear contextual guidance on when to use this tool. It does not explicitly name exclusions or alternative tools, but the domain and purpose are clear enough for selection.

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