Skip to main content
Glama

Begin undo group

gimp_begin_undo_group

Starts grouping image edits into one GIMP undo step so multiple changes undo together; close the group later with the matching end call.

Instructions

Start grouping the following changes to an image into ONE step of GIMP's undo history (what Ctrl+Z undoes in GIMP's UI). Close it with gimp_end_undo_group. Groups nest. If this client disconnects, its open groups are closed automatically. Grouping is not a transaction: nothing is rolled back on error (use checkpoints for that).

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>"
    },
    "name": "gimp_begin_undo_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesImage id from gimp_status, e.g. 'image:1@a1b2c3d4'.
labelNo

Output Schema

NameRequiredDescriptionDefault
depthYesUndo groups this client still has open on the image (0 = none).
imageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses lifecycle behavior, nesting, disconnect cleanup, and the important non-transactional error semantics. These are exactly the behavioral details an agent needs before wrapping edits in a group.

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 short and front-loaded, with each sentence adding distinct operational value: purpose, closing mechanism, nesting, disconnect cleanup, and non-transactional behavior.

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?

It covers the operational and lifecycle context well, and an output schema exists so return values need not be explained. The main gap is that the description says nothing about the label parameter, leaving one of two parameters semantically unexplained.

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 coverage is only 50%: image is documented in the schema, but label has no description in either the schema or the tool description. The description does not explain what label controls, whether it affects the undo-history display, or whether it is optional/cosmetic.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: grouping following image changes into one undo-history step. It clearly distinguishes this setup operation from the closing sibling gimp_end_undo_group and from checkpoints.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says how to close the group, notes that groups nest, explains automatic closing on client disconnect, and clarifies when not to expect transactional rollback by pointing to checkpoints instead.

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