lentera-aseprite-mcp

set_frame_duration

Set the duration of an animation frame in milliseconds to control playback timing, such as 125ms for walks or 80-200ms for attacks.

Instructions

Set the duration of a specific frame. Lentera walk=125ms (8fps), attack varies per 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": {
      "frame_number": "<frame_number>",
      "duration_ms": "<duration_ms>"
    },
    "name": "set_frame_duration"
  }
}

Input Schema

Name	Required	Description	Default
`duration_ms`	Yes	Duration in ms. Walk: 125ms. Attack strike: 150-200ms. Attack others: 80-100ms.
`frame_number`	Yes	Frame number (1-based)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 14, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations, the description must carry the behavioral disclosure burden. It states the action and provides typical duration values, but does not disclose side effects, prerequisites (e.g., frame existence), or error handling. The second sentence largely repeats schema parameter descriptions rather than adding operational context.

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, with the primary purpose front-loaded and no filler. Every sentence contributes to clarifying the tool's function and typical values.

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 simple two-parameter setter with no output schema and fully documented parameters, the description is largely sufficient. It clearly identifies the action and provides domain-specific values, though it could mention what happens if the frame number is invalid.

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

Parameters3/5

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

The input schema already documents both parameters with 100% coverage. The description adds only the 8fps equivalence for walk duration, which is marginal value beyond the schema. Baseline 3 is appropriate since the description does not significantly enhance parameter understanding.

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 clearly states a specific action ('Set the duration') and a specific resource ('a specific frame'). It distinguishes itself from sibling frame-related tools like add_frame, remove_frame, and set_active_frame by focusing on duration modification.

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

Usage Guidelines3/5

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

No explicit when-to-use or alternative comparison is provided, but the Lentera walk/attack examples imply the tool is used for animation timing. Since no sibling tool handles frame duration, the missing alternative guidance is less critical, but the usage context is still only implied.

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