Skip to main content
Glama
Sign In
gimp-mcp

gimp-mcp

by abelduarte
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gimp.fill_rect

Fill a rectangular region on a GIMP drawable using the foreground color. Provide coordinates, width, and height to paint a solid rectangle.

Instructions

Fill a rectangular region on a drawable using the foreground 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": {
      "image_id": "<image_id>",
      "drawable_id": "<drawable_id>",
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "gimp.fill_rect"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_idYes
drawable_idYes
xYes
yYes
widthYes
heightYes
colorNoCSS color string, [r,g,b], [r,g,b,a], or {r,g,b,a}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

Without annotations, the description must disclose behavioral traits. It only says 'fill', but does not explain whether this modifies the drawable in place, overwrites existing pixels, creates a new layer, or requires undo steps. The mutability is implied but not detailed.

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

Conciseness3/5

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

The description is a single sentence with no extraneous words, but it is too brief given the tool's complexity (7 parameters). It could be slightly expanded without losing conciseness.

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?

For a tool with 7 parameters, no output schema, and only 14% schema description coverage, the description is incomplete. It lacks return value information, side effects, and clarity on required parameter semantics beyond the basic action.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 14% (only 'color' has a description). The tool description adds 'foreground color' context, which is not in the schema, but it doesn't explain other parameters like image_id, drawable_id, coordinates, or dimensions. The color parameter description in the schema is detailed, but overall parameter semantics are weak.

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 clearly states the action (fill), the target (rectangular region on a drawable), and the method (using foreground color). It distinguishes from the sibling 'gimp.fill_ellipse' by specifying rectangle shape. However, it could be more precise about the source of foreground color.

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 on when to use this tool vs alternatives like 'gimp.fill_ellipse' or 'gimp.set_layer_properties'. No prerequisites (e.g., drawable must exist, be active) or caveats (e.g., color mode limitations) are mentioned.

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