Skip to main content
Glama

draw_brush

Stamp a custom brush shape at defined points in an Aseprite sprite. Specify brush pattern as character rows, positions, color, and anchor offset.

Instructions

Stamp a custom brush shape at a list of points.

Args:
    brush: The brush as rows of characters. Any character other than space,
        '.', or '0' is a filled cell. e.g. a plus brush: ["010", "111", "010"].
    points: Positions to stamp at, list of {"x": int, "y": int}.
    color: Colour to stamp the brush in.
    anchor: "center" (default) or "topleft" — where each point sits in the brush.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brushYes
colorYes
frameNo
layerNo
anchorNocenter
pointsYes
filenameYes
Behavior3/5

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

No annotations exist, so description carries full burden. It explains brush format, anchor option, and point positions, but does not mention behaviors like overwriting vs blending, or effect on frame/layer parameters present in schema.

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?

Description is well-structured as a docstring with clear Args section. It is concise but could front-load the purpose more. Each sentence adds value, though the Args format is slightly verbose.

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

Completeness2/5

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

Given no output schema and no annotations, the description lacks details on return value (void? success?), side effects (modifying sprite), and interaction with frame/layer. Incomplete for a tool with 7 parameters and 0% schema coverage.

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 has 0% description coverage. Description covers brush, points, color, and anchor with meaning beyond types. However, it omits filename (required), frame, and layer, leaving 3 parameters undocumented.

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?

Description clearly states 'Stamp a custom brush shape at a list of points,' which is a specific verb+resource. It distinguishes from sibling drawing tools like draw_pixels and draw_line by focusing on custom brush shapes.

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?

The description implies usage for custom shape stamping but does not explicitly guide when to use this tool versus alternatives like draw_pixels or fill_area. No exclusions or when-not-to-use guidance provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MalloyTheDev/aseprite-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server