Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

stop_recording

Stops the Aseprite recording session and exports the captured timelapse as a looping GIF to the specified path, with sharp-pixel zoom and configurable frame timing and maximum size.

Instructions

Stop recording and write the timelapse GIF to out_path. It's zoomed with sharp pixels to fit max_size, and the final picture holds for a beat before it loops. Larger GIFs take longer to encode, so raise max_size with care.

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": {
      "out_path": "<out_path>"
    },
    "name": "stop_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
frame_msNo
max_sizeNo
out_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare destructiveHint=false and openWorldHint=true, so the description adds real value by disclosing that this writes a file to disk, that output is zoomed with sharp pixels, that the last frame holds before looping, and that encode time grows with max_size. It stops short of saying whether an existing file at out_path is overwritten, which is the main remaining behavioral risk.

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

Conciseness4/5

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

Three sentences, front-loaded with the action and destination, then output characteristics, then a cost warning. The 'holds for a beat before it loops' phrasing is slightly informal but conveys genuine output behavior rather than padding.

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?

With no output schema and zero parameter descriptions, the definition does cover the return artifact and encoding cost well. It is still incomplete for a file-writing tool: frame_ms is unexplained and the overwrite/failure behavior of out_path is not addressed.

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?

Schema coverage is 0%, so the description carries the burden and partially meets it: out_path is identified as the write destination and max_size is tied to output size and encoding time. However, frame_ms is never mentioned and max_size's units/interpretation remain unspecified, leaving one of three parameters completely opaque.

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 names a specific verb and resource ('Stop recording and write the timelapse GIF') plus the destination parameter, so the agent knows exactly what the tool produces. It never explicitly contrasts itself with 'start_recording', but the name pair makes the lifecycle relationship self-evident.

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?

Usage is only implied: the agent must infer this is called to finalize an in-progress recording, and the caution 'raise max_size with care' is a useful operational tip. There is no statement of prerequisites (e.g., what happens if no recording is active) or when-not-to-use guidance.

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