Skip to main content
Glama
pixelorama-mcp
by Aeroscoop

fill_rect

Fill a rectangular area with a specified color on a chosen layer and frame; omit position and size to fill the whole canvas.

Instructions

Fill a rectangle with one color. Leave out the position and size to fill the whole canvas.

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": {
      "color": "<color>"
    },
    "name": "fill_rect"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
colorYesColor as #rgb, #rrggbb, #rrggbbaa, a name like "red", "transparent", or "@n" for slot n (from 0) of the selected palette
frameNoFrame index, from 0. Defaults to the current frame
layerNoLayer index, 0 is the bottom layer. Defaults to the current layer
widthNo
heightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: it does not say that existing pixels on the target layer/frame are overwritten, whether the operation is undoable, how frame/layer defaults resolve, or whether the fill is affected by a selection. Only the word "fill" hints at destructive overwrite, which is not enough 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.

Conciseness4/5

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

Two short sentences, front-loaded with the core action and followed by the one non-obvious rule. Nothing is padded; the gap is under-specification, not verbosity.

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 7 parameters, 43% schema coverage, no annotations, and no output schema, the description needs to do more. It leaves the agent without knowledge of the destructive overwrite semantics, the coordinate system for x/y, or what happens when only some of the optional geometry parameters are supplied.

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 43% (only color, frame, and layer are documented there). The description compensates for exactly the undocumented group by stating that omitting position and size fills the whole canvas, which explains the optionality of x/y/width/height. However, it adds no meaning for the coordinate origin, width/height units, or the frame/layer interaction beyond what the schema already says.

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?

"Fill a rectangle with one color" gives a specific verb (fill) plus a resource (rectangle) and an implied effect (solid color). It is distinguishable from draw_pixels and clear_cel by the rectangle+single-color scope, though it never names those siblings explicitly.

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 second sentence splits usage into two modes: rectangle fill when position/size are given, whole-canvas fill when they are omitted. That is useful implied guidance, but there is no statement of when to prefer this over clear_cel or draw_pixels, and no prerequisites or exclusions.

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