Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

sharpen

Apply an unsharp mask to the active cel to crisp pixel edges while avoiding halos around transparency; adjust strength from 0.1 to 2.0 in one undo step.

Instructions

Sharpen the active cel (unsharp mask over a 3x3 neighborhood). strength 0.1-2.0. Only opaque pixels are considered, so sprite edges don't halo against transparency. One undo step.

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

Input Schema

NameRequiredDescriptionDefault
fileNo
strengthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

With only a title annotation, the description carries the disclosure burden, and it does add real behavior: only opaque pixels are sampled so edges don't halo against transparency, and the result is one undo step (i.e., reversible). It still omits what the tool returns, whether non-opaque pixels are preserved untouched, and whether performance/region limits apply.

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 short, front-loaded sentences: operation, algorithm, parameter range, edge-case behavior, undo. Every sentence carries information, with no filler; only minor tightening would be possible.

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 filter with no annotations and no output schema, the description covers the core mechanics, the alpha-handling edge case, and undo semantics. The remaining gap is the undocumented ``file`` parameter and the response shape, which keeps it short of full completeness.

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 carry parameter meaning, and it only covers one of two parameters: it constrains ``strength`` to 0.1-2.0 (adding a range beyond the schema) but never states the default of 0.5. The ``file`` parameter is entirely unexplained, leaving the agent to guess what null means versus an explicit path.

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 verb and target ("Sharpen the active cel") and pins down the algorithm ("unsharp mask over a 3x3 neighborhood"), so an agent knows exactly what operation runs. It does not differentiate itself from other pixel-effect siblings such as box_blur, relying on the reader to infer sharpen-vs-blur from the verb.

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 implied by "sharpen" and by the target being the active cel, so an agent can infer it applies to the current layer's pixels. There is no explicit when-to-use, no prerequisites (e.g., must a cel be selected or a file specified), and no mention of alternatives for other smoothing/sharpen-style effects.

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