Skip to main content
Glama
Sign In
pixel-mcp

pixel-mcp

by adrianoamaral
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fill_rect

Draw a solid-color rectangle on a pixel art canvas by specifying position, dimensions, and color. Use it to add shapes or backgrounds programmatically.

Instructions

Fill a rectangle with a solid color.

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

Input Schema

NameRequiredDescriptionDefault
xYesTop-left X
yYesTop-left Y
colorYesFill color
widthYesRectangle width
canvasNoCanvas namedefault
heightYesRectangle height

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the burden of explaining behavior. 'Fill a rectangle with a solid color' communicates the core mutation, but does not disclose effects on existing pixels, canvas selection semantics, or coordinate/clipping behavior. A 3 is appropriate for minimal viable transparency.

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?

The description is a single, front-loaded sentence with no filler words. It directly names the action and the target resource, earning every word it uses.

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 drawing primitive, this is adequate alongside a fully described schema, but it lacks usage routing and behavioral caveats. The absence of annotations and an output schema means the description could add more context about effects and alternatives.

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 100%, so the schema already documents x, y, width, height, color, and canvas. The description only adds the concept of a solid-color fill, which does not meaningfully expand on the parameter semantics already present. 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 states a specific action and resource: filling a rectangle with a solid color. This clearly distinguishes it from sibling tools like set_pixel, draw_line, and clear, even though it does not explicitly name them.

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 gives no explicit guidance about when to use fill_rect instead of set_pixel, draw_line, or clear. Usage is only vaguely implied by the tool name and the action described, not explained.

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

Deploy Server

Other Tools