Aseprite-MCP

by iborymagic

Overview Schema Source Related Servers Discussions Admin

TypeScript

get_frame_info

Retrieve details about the current frame in an Aseprite file, including frame index, duration, and layer visibility.

Instructions

Gets information about the current frame

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": {
      "inputFile": "<inputFile>"
    },
    "name": "get_frame_info"
  }
}

Input Schema

Name	Required	Description	Default
`inputFile`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jul 5, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states a read operation without disclosing side effects, permissions, or what 'information' includes. This is minimal disclosure.

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

Conciseness3/5

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

The description is very concise but at the cost of being under-specified. It lacks necessary detail, making it minimally informative despite its brevity.

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

Completeness1/5

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

With one undocumented parameter and no output schema, the description is incomplete. It does not clarify return values, parameter format, or behavior, leaving agents needing additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage and the description fails to explain the 'inputFile' parameter. With no additional meaning beyond the schema, this is a severe gap.

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 'Gets information about the current frame' clearly states the verb and resource. However, it does not explicitly differentiate from sibling tools like get_active_sprite_info or get_layer_list, though the focus on 'frame' is implicit differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There are no prerequisites, exclusions, or context about the current frame concept mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.