Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

set_symmetry

Idempotent

Set mirror-painting symmetry in Aseprite by choosing none, horizontal, vertical, or both modes and optionally placing axis lines, so subsequent brush strokes mirror automatically.

Instructions

Live editor only: set mirror-painting symmetry — mode is none, horizontal (mirror across a vertical axis), vertical, or both; optionally place the axis lines. Affects the artist's subsequent brush strokes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mode": "<mode>"
    },
    "name": "set_symmetry"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
x_axisNo
y_axisNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only supply idempotentHint=true, so the description carries most of the burden and does add real context: the effect is stateful and applies to the artist's subsequent brush strokes, and the tool is restricted to a live editor session. It does not say whether symmetry persists across sprite/cel changes or resets, which is the remaining behavioral gap.

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?

Short and front-loaded, with the hard constraint ('Live editor only') placed first and the mode enumeration immediately after. Every clause carries information; only the mode list could be tightened into a more scannable form.

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 three-parameter setter with no output schema and zero schema documentation, the description covers the primary parameter thoroughly and flags the persistence semantics. The unstated coordinate semantics for the axis parameters and the reset behavior are the only material omissions.

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 and it partly does: it defines all four mode values with the axis orientation spelled out. The x_axis/y_axis parameters get only 'optionally place the axis lines', with no coordinate space, units, or mapping between each parameter and the mode that uses it.

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 ('set mirror-painting symmetry') and enumerates the full mode vocabulary, so an agent knows exactly which setting is changed and what values are legal. The parenthetical 'horizontal (mirror across a vertical axis)' resolves the naming ambiguity that would otherwise confuse selection.

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?

'Live editor only' is a genuine precondition that tells the agent when this tool is callable and when it is not. Beyond that there is no guidance on alternatives or on which mode to pick for a given drawing task, so usage is only implied.

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