Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

invert_selection

Invert the active selection to target everything outside it within the canvas bounds, useful for isolating or editing the unselected area.

Instructions

Invert the current selection against the canvas bounds.

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

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations supply only idempotentHint=false and a title, so the description carries most of the burden. "Against the canvas bounds" hints that the result is the complement region clipped to the canvas, but the description never says what happens when nothing is selected, whether existing selection is replaced, or whether the operation is undoable.

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?

One short sentence, front-loaded with the action and resource, with no filler. Its brevity is efficient, though it edges toward under-specification rather than verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with an optional scoping parameter, no output schema, and near-empty annotations, the description omits both the parameter's role and the no-selection edge case. An agent cannot determine correct invocation conditions or the effect of passing "file" from this definition alone.

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% and the single "file" parameter (string or null, optional) is never mentioned in the description, so its meaning and effect on the operation are undocumented in both places. The description adds no parameter meaning beyond the raw schema.

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 resource ("Invert the current selection") and adds scope ("against the canvas bounds"), which lets an agent distinguish it from a color-inversion tool like invert_colors. It stops short of explicitly naming any sibling, so differentiation is inferred 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g. an existing selection), and no pointer to alternatives such as get_selection or edit_in_selection. The agent must guess the operating context entirely.

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