Skip to main content
Glama
pixelorama-mcp
by Aeroscoop

resize_canvas

Change the canvas dimensions without scaling the artwork, using an anchor to control where the existing image stays within the new bounds.

Instructions

Change the canvas size without scaling. anchor is where the old image stays: bottom (default, centered horizontally), top, center, left, right, or combinations like bottom-left.

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": {
      "width": "<width>",
      "height": "<height>"
    },
    "name": "resize_canvas"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYes
anchorNo
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that content is not scaled and that the existing image is positioned according to anchor, which is real behavioral information. However, it omits what happens to content when the canvas shrinks (cropping) or grows (fill color/transparency), and whether the operation is undoable — significant gaps for a mutation tool with zero annotation coverage.

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?

Two tight sentences, front-loaded with the core action and immediately followed by the parameter that actually needs explanation. No filler or restatement of the tool name.

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 simple three-parameter tool with no output schema the definition is mostly sufficient, especially around anchor. But without annotations it should still say what fills newly exposed canvas area and what happens to pixels that fall outside a shrunken canvas, since those determine whether the call is safe.

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 0%, so the description must compensate. It does this well for the non-obvious parameter, enumerating anchor values, stating the default ('bottom, centered horizontally'), and explaining the semantics ('where the old image stays'). Width and height are left to their self-explanatory names, with bounds only visible in the schema, which is a minor gap.

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 and resource ('Change the canvas size') and adds the crucial qualifier 'without scaling,' which distinguishes it from any resize-by-scaling operation. No sibling tool overlaps this behavior, so explicit sibling differentiation isn't needed, but the description also doesn't name any adjacent operation (e.g., add_frame) to orient the agent.

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 'without scaling' phrase implies the intended context (extending/trimming the canvas while preserving pixel scale), but there is no explicit statement of when to choose this over other operations or any prerequisite/exclusion. Usage must be inferred from the semantics rather than read from the text.

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