Skip to main content
Glama
MalloyTheDev

Aseprite MCP

by MalloyTheDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_outline

Add a pixel outline around artwork on a layer, controlling color, thickness, and whether it grows outside or recolors the border inward.

Instructions

Add a pixel outline around the artwork on a layer.

Args:
    color: Outline colour.
    thickness: Outline width in pixels (default 1).
    connectivity: 4 (orthogonal only) or 8 (includes diagonals, default).
    where: "outside" (grow into transparency, default) or "inside"
        (recolour the shape's border pixels).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorYes
frameNoDefault: 1.
layerNo
whereNoDefault: "outside".outside
filenameYes
thicknessNoDefault: 1.
connectivityNoDefault: 8.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv0.10.0
    • removedInput schema / properties / color / title
      Removed value: -"Color"
    • addedInput schema / properties / connectivity / description
      Added value: +"Default: 8."
    • removedInput schema / properties / connectivity / title
      Removed value: -"Connectivity"
    • removedInput schema / properties / filename / title
      Removed value: -"Filename"
    • addedInput schema / properties / frame / description
      Added value: +"Default: 1."
    • removedInput schema / properties / frame / title
      Removed value: -"Frame"
    • removedInput schema / properties / layer / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / layer / default
      Removed value: -null
    • removedInput schema / properties / layer / title
      Removed value: -"Layer"
    • addedInput schema / properties / layer / type
      Added value: +"string"
    • addedInput schema / properties / thickness / description
      Added value: +"Default: 1."
    • removedInput schema / properties / thickness / title
      Removed value: -"Thickness"
    • addedInput schema / properties / where / description
      Added value: +"Default: \"outside\"."
    • removedInput schema / properties / where / title
      Removed value: -"Where"
    • removedInput schema / title
      Removed value: -"add_outlineArguments"
  2. First observedv0.7.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare readOnlyHint false and openWorldHint false, establishing a local write operation. The description adds semantics for the where option (outside grows into transparency, inside recolours border) but does not state that the layer is modified in place or whether existing artwork is required.

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?

Front-loaded purpose followed by a structured Args list. Concise and readable, though it repeats schema defaults for thickness, connectivity, and where.

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 7-parameter mutation tool with no output schema, the description covers the main operation and key parameters but leaves filename, layer, and frame undocumented. It also does not clarify which layer is modified if 'layer' is omitted.

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 description coverage is 57% and the schema descriptions are only default values. The description provides meaningful semantics for color, thickness, connectivity, and where, but omits filename, layer, and frame. This adds substantial value for the core outline parameters.

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 (add) and resource (pixel outline) plus target (artwork on a layer). It does not differentiate from the sibling tool outline_smart, so sibling differentiation is absent.

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?

No when-to-use guidance or alternatives are provided; the description only documents parameters. An agent must infer context from the tool name and siblings.

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