Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

explain_changes

Read-only

Maps recent Aseprite edits to the matching tool, menu command, or default shortcut so you can reproduce Claude's actions and learn the technique.

Instructions

Say which Aseprite tool, menu, or shortcut would do what Claude just did, so you pick up the technique. Covers the last most recent edits, newest repeats merged. Shortcuts are Aseprite's defaults.

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

Input Schema

NameRequiredDescriptionDefault
lastNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds behavior the annotations do not: edits are capped to the most recent ones, duplicate repeats are merged, and reported shortcuts reflect Aseprite defaults rather than any custom keymap — a real caveat that affects how an agent should interpret results.

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 clauses, front-loaded with the core purpose and followed by two scoping caveats; every sentence carries information. The stray markup around ``last`` is cosmetic noise but not confusing.

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?

This is a simple read-only tool with one optional parameter and no output schema, so the description only needs purpose plus scoping caveats, both of which are present. The one remaining gap is that it does not hint at the shape of the reply (per-edit breakdown versus a single summary).

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

Parameters4/5

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

Schema coverage is 0% and the single 'last' parameter is otherwise undocumented, so the description must carry the burden. It does explain that 'last' governs how many of the most recent edits are covered and that repeats are merged, though it never states the default value or any upper bound.

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?

States a specific action (name the Aseprite tool, menu, or path for what was just done) on a specific resource (the recent edit history), and the purpose is legible enough to separate it from a raw change feed. It stops short of explicitly contrasting itself with siblings such as get_watched_changes, so the distinction is inferable rather than stated.

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?

Timing is implied by 'would do what Claude just did, so you pick up the technique' and by the scope of recent edits, but there is no explicit when-to-use-this vs. when-to-use-something-else guidance. An agent can guess this is for post-edit explanation, but nothing tells it to prefer get_watched_changes for raw diffs.

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