Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

start_recording

Idempotent

Begins capturing the active frame after each edit so the session can be turned into a GIF timelapse; pass a file to record headlessly.

Instructions

Start recording this session: a picture of the active frame is kept after every edit, for stop_recording to turn into a GIF timelapse. Each picture is one more read of the sprite, so edits run a little slower while it's on. Starting again throws away what's recorded. Headless: pass file.

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

Input Schema

NameRequiredDescriptionDefault
fileNo
max_framesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the sparse annotations (idempotentHint only) by disclosing the side effect on edits (slower, one extra sprite read per edit), the destructive restart behavior, and the headless-mode requirement. These are exactly the traits an agent needs before deciding to enable recording.

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?

Four tight sentences, front-loaded with the core purpose, then cost, then restart semantics, then the headless note. No filler; the 'one more read of the sprite' aside justifies itself by explaining the performance cost.

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 two-parameter, no-output-schema toggle, the description covers purpose, cost, restart semantics, and the headless path. The only real hole is the unexplained `max_frames` cap, which matters for long sessions.

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 description coverage is 0%, so the description must compensate. It explains `file` as the headless-mode target, which is genuinely additive, but `max_frames` (default 300) is never mentioned, leaving half the parameters undocumented anywhere.

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?

States a specific verb and resource ('Start recording this session') and immediately explains the mechanism (a picture of the active frame is kept after every edit). It also names the sibling that consumes the result, stop_recording, so an agent can distinguish the two without inspecting schemas.

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?

Clear context for use: turn it on, do edits, then hand off to stop_recording for a GIF timelapse, and pass `file` when running headless. It also warns that starting again discards prior footage, which is the main misuse hazard. It stops short of explicit when-not-to-use guidance (e.g. cost tradeoffs for long sessions).

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