gimp-mcp

Overview Schema Source Related Servers Discussions Admin

Flip layer

gimp_flip_layer

Mirror a layer or group horizontally or vertically around its center to reverse orientation without quality loss in one undo step.

Instructions

Mirror a layer or group horizontally or vertically around its center. Lossless. 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": {
      "item": "<item>",
      "direction": "<direction>"
    },
    "name": "gimp_flip_layer"
  }
}

Input Schema

Name	Required	Description	Default
`item`	Yes	Item id (layer, group, mask...) e.g. 'item:5@a1b2c3d4'.
`direction`	Yes

Output Schema

Name	Required	Description
`x`	Yes	Offset of the layer's top-left corner in image pixels.
`y`	Yes
`id`	Yes
`kind`	Yes
`mask`	Yes
`mode`	Yes	GIMP layer mode nick, e.g. 'normal', 'multiply'.
`name`	Yes	Layer name. GIMP keeps names unique within an image ('Title #1').
`locks`	Yes
`width`	Yes
`height`	Yes
`parent`	Yes	Id of the parent group, null at the top level.
`opacity`	Yes	0-100.
`visible`	Yes
`children`	No	Child layers of a group, top-most first; null for non-groups.
`has_alpha`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.6.0Nov 10, 2026

changedOutput schema / $defs / LayerNode / properties / kind / enum

Previous value: -[
-  "layer",
-  "group",
-  "text"
-]New value: +[
+  "layer",
+  "group",
+  "text",
+  "vector",
+  "link"
+]

changedOutput schema / properties / kind / enum

Previous value: -[
-  "layer",
-  "group",
-  "text"
-]New value: +[
+  "layer",
+  "group",
+  "text",
+  "vector",
+  "link"
+]

First observedv0.1.0Nov 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the annotations (destructiveHint=false, readOnlyHint=false), the description discloses 'Lossless' and 'One undo step' – real behavioral facts the agent could not derive from structured fields, telling it the mutation is reversible and safe to retry. It does not say what happens to masks within a flipped group, so it is not exhaustive.

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, front-loaded sentences with zero waste: operation, quality guarantee, undo cost. The clipped fragments 'Lossless.' and 'One undo step.' each carry 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 two-parameter, low-complexity tool with an output schema, the definition covers what it does, that it is lossless, and that it costs one undo step – enough to call it correctly. Minor omissions (mask behavior, group semantics) remain but are not blocking.

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?

The description repeats the two direction values ('horizontally or vertically') and adds the pivot ('around its center'), which is the one piece of meaning the schema does not convey. The 'item' parameter is only documented by the schema, so the description does not compensate for the 50% coverage gap.

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 plus resource ('Mirror a layer or group') and the two axes, so the agent knows exactly what operation is performed. It does not explicitly differentiate itself from geometry-ish siblings like gimp_rotate_layer or gimp_scale_layer, which keeps it short of a 5.

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: the agent can infer 'use when you want to flip a layer', but there is no explicit when-to-use, when-not-to-use, or reference to the rotate/scale alternatives. Adequate but with a clear gap.

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

Deploy Server