Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

select_frame

Idempotent

Sets the active animation frame so subsequent edits apply to it. Use it as a step in edit_batch for headless sessions, which reset frame state between calls.

Instructions

Make a frame active, so the next edits land on it. Headless forgets this between calls, so use it as a step in edit_batch there.

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": {
      "number": "<number>"
    },
    "name": "select_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior5/5

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

Beyond idempotentHint, it discloses that activation controls the target of subsequent edits and that headless calls do not retain this state. The non-persistence behavior and its operational consequence are important, non-obvious details for correct invocation.

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?

Two short sentences front-load the purpose and then present the headless exception. Every clause contributes actionable information, with no filler or repetition of structured fields.

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?

For a simple two-parameter tool, the description explains the central stateful workflow and headless limitation well. However, the undocumented file and number inputs prevent fully confident invocation across files or valid frame ranges, and no output schema supplies 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?

With 0% schema description coverage, the description needed to compensate but mentions neither parameter. It leaves number's indexing and valid range, as well as file's meaning and default-target behavior when null, unspecified.

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?

“Make a frame active” states a specific action and resource, while “so the next edits land on it” explains the practical effect. It does not explicitly distinguish frame activation from sibling selectors such as select_layer, so sibling differentiation remains implicit.

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?

The description says to use the tool before edits that should target a frame and gives a concrete headless workflow: include it as a step in edit_batch. This supplies both conditional guidance and an alternative to relying on a separate preceding call.

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