Skip to main content
Glama
Sign In
gimp-mcp

gimp-mcp

by mhbxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Scale image

gimp_resize_image
Destructive

Scales an entire GIMP image and all its layers to a specified width and height, resampling pixels with selectable interpolation in one undoable step.

Instructions

Scale the whole image and every layer to width x height pixels (layer sizes and offsets scale proportionally). Lossy: pixels are resampled with the given interpolation. One undo step.

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": "<image>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "gimp_resize_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesImage id from gimp_status, e.g. 'image:1@a1b2c3d4'.
widthYesPixels.
heightYesPixels.
interpolationNoResampling: none (nearest neighbour, hard edges), linear, cubic, nohalo, lohalo.cubic

Output Schema

NameRequiredDescriptionDefault
dirtyYes
imageYes
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety bar is lower. The description still adds real value by disclosing that the operation is lossy (pixels resampled), that layer sizes and offsets scale proportionally, and that it consumes exactly one undo step.

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 with the scope, the lossy resampling caveat, and the undo cost front-loaded. Every clause carries information an agent needs before invoking a destructive scale.

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?

An output schema exists and annotations cover the destructive profile, so the description need not explain returns. It covers scope, proportionality, lossiness, and undo cost, though it omits any prerequisite about valid image ids (left to the schema) or interaction with undo groups.

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 image, width, height, and the interpolation enum are fully documented structurally. The description reinforces the pixel units and that interpolation governs the resampling, but adds no format or constraint detail beyond the schema, making baseline 3 appropriate.

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 scope: 'Scale the whole image and every layer to width x height pixels', which implicitly separates it from gimp_scale_layer (single layer) and gimp_resize_canvas (no resampling). It stops short of naming those siblings, so the differentiation requires the agent to infer it.

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?

Usage is only implied through the scope phrase 'whole image and every layer'. There is no explicit when-to-use or when-not-to-use guidance pointing to gimp_scale_layer, gimp_resize_canvas, or gimp_crop_image, which are the obvious alternatives in this sibling set.

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