Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

look_onion

Read-only

Renders an animation frame with earlier frames ghosted red and later frames blue to show the full motion arc at once; pass a file for headless use.

Instructions

See motion: returns frame as an image with earlier frames ghosted in red and later frames in blue, so the whole arc shows at once. Defaults to the active frame. The picture form of render_onion_composite. 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": "look_onion"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
nextNo
prevNo
frameNo
scaleNo
opacityNo
max_sizeNo
backgroundNochecker

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries real weight and delivers: it describes the rendered output (ghosted red/blue frames), the default frame selection, and the headless file-export path. It stops short of saying where the image goes in interactive mode or how `prev`/`next`/`opacity` affect the render.

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 short sentences, front-loaded with the visual result, then the default, then the alternative/headless mode. No filler. The opening 'See motion:' is a slightly odd fragment but sets context efficiently.

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 read-only render tool with no output schema, the description adequately conveys what the result looks like and how to get it headlessly. It is incomplete for an 8-parameter tool: half a dozen tuning knobs (span of frames, scale, opacity, max size, background) are undocumented anywhere, leaving an agent to guess at their effect.

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

Parameters2/5

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

Schema description coverage is 0% across 8 parameters, so the description must compensate. It explains only `frame` (defaults to active) and `file` (headless export); `next`, `prev`, `scale`, `opacity`, `max_size`, and `background` are left entirely opaque, including the default checkerboard background.

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 uses a specific verb and outcome: returns `frame` as an image with earlier frames ghosted red and later frames blue. It also names a sibling (`render_onion_composite`) to position itself against. The remaining ambiguity is that 'the picture form of render_onion_composite' doesn't clearly explain how the two differ, since the sibling name also implies a picture.

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?

It states a default ('defaults to the active frame') and a mode switch ('Headless: pass `file`'), which implies when to use it for export versus on-screen viewing. However, it never says when to prefer this over `look`, `look_animation`, or `render_onion_composite`. Usage is inferable but not explicit.

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