Skip to main content
Glama

resize_canvas

Resizes the canvas without redrawing, keeping existing art anchored. Grows with blank padding or crops to add margins, reposition drawings, or make room before compositing.

Instructions

Resize the canvas without redrawing — keep the existing art and re-anchor it. Growing pads with blanks; shrinking crops what falls outside. Use it to add margin, reposition a drawing, or make room before compositing.

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
widthYesNew canvas width in cells.
anchorNoWhere to hold the existing art as the canvas resizes.top-left
heightYesNew canvas height in cells.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that existing art is preserved and re-anchored, that growth pads with blanks, and that shrinking discards content outside the new bounds — the destructive consequence is stated plainly. It doesn't address reversibility, limits, or what the tool returns, which are the remaining gaps.

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 short sentences, front-loaded with the non-destructive guarantee, then behavior, then use cases. No redundant or filler wording; each clause contributes distinct information.

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

Completeness4/5

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

For a three-parameter mutation tool with no annotations and no output schema, the description covers the essential behavior an agent needs: art preservation, padding versus cropping, and anchoring. A note on whether the operation is undoable or what is returned would make it fully self-sufficient.

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 coverage is 100%, so width, height, and anchor are already fully documented, including the anchor enum and the 1–400 range. The description only restates the anchor concept ('re-anchor it') and the pad/crop semantics of the dimensions, adding little beyond the schema. Baseline 3 applies.

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?

The description pairs a specific verb and resource ('Resize the canvas') with the key differentiator 'without redrawing — keep the existing art', which separates it from destructive siblings like new_canvas or clear_canvas. It stops short of naming any sibling, and notably does not distinguish itself from crop, even though it describes shrinking as 'crops what falls outside'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete use cases: add margin, reposition a drawing, make room before compositing. That is clear context for when to reach for it, but there are no explicit when-not conditions and no named alternative (e.g., use crop instead when you want to trim without re-anchoring).

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