Skip to main content
Glama

resize_canvas

Resize pixel art canvas by setting new dimensions, positioning existing content with an anchor point, and filling new area with transparency. Clears saved selections.

Instructions

Resize the canvas. Existing content is placed according to the anchor; new area is transparent. Clears saved selections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthYes
anchorNoWhere existing content sits in the new canvas (default center)
doc_idYesDocument id
heightYes
renderNoInclude a render of the change (default true)
Behavior3/5

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

With no annotations, the description reveals important behaviors: content placement via anchor, transparent new area, and clearing saved selections. However, it does not disclose what happens when width/height is smaller than current canvas (e.g., cropping), nor any permissions or undo behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with no extraneous content. The most critical information is front-loaded: 'Resize the canvas'.

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?

The description covers anchor behavior and selection clearing, but omits details on cropping when dimensions decrease, the render parameter, and return value. Given five parameters and no output schema, more detail is expected.

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 60%. The description mentions 'anchor' and 'transparent new area', which adds context but does not fully compensate for the missing parameter descriptions. The schema already describes anchor and render, but width/height lack descriptions; the description does not clarify them.

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 explicitly states 'Resize the canvas' which is a specific verb and resource. It distinguishes from siblings by detailing unique behaviors like anchor placement and clearing selections, which are not found in other sibling tools.

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 guidance is provided on when to use this tool vs alternatives. There is no mention of prerequisites, when not to use, or comparisons to sibling tools like shift_layer or mirror_region.

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/ehm-93/pixel-mcp'

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