Skip to main content
Glama

draw_line

Draw a straight line between two points on a sprite, with options for pixel-perfect rendering or antialiasing.

Instructions

Draw a straight line from (x1,y1) to (x2,y2).

Args:
    pixel_perfect: Remove L-shaped corner pixels for a clean 1px pixel-art line.
    antialias: Smooth (Xiaolin Wu) line with alpha blending — RGB sprites only;
        ignored on indexed/gray. Takes precedence over pixel_perfect.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
x1Yes
x2Yes
y1Yes
y2Yes
colorYes
frameNo
layerNo
filenameYes
antialiasNo
pixel_perfectNo
Behavior4/5

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

The description explains that antialias is ignored on indexed/gray sprites and takes precedence over pixel_perfect. This adds transparency beyond the mere action of drawing. However, it does not mention other behavioral aspects like pixel blending or layer interaction.

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?

The description is concise, with a clear Args section. It avoids unnecessary details but could be slightly more efficient. Every sentence adds value.

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?

With 10 parameters and no output schema, the description is incomplete. It does not explain the purpose of filename, frame, layer, or color format. Users may still be unsure about how to use the tool correctly.

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?

The description adds meaning to pixel_perfect and antialias parameters with detailed explanations. However, it omits explanation for required parameters like filename, frame, layer, and color, which are not covered in the schema descriptions. Schema coverage is 0%, so the description compensates partially.

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?

The description clearly states the tool draws a straight line between two points, with specific parameter details. It distinguishes itself from sibling tools like draw_curve or draw_polyline by focusing on a single straight line.

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?

The description does not provide guidance on when to use this tool versus alternatives such as draw_curve or draw_rectangle. It assumes the user wants a straight line without specifying context or exclusions.

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