Skip to main content
Glama
Sign In
gimp-mcp

gimp-mcp

by mhbxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List checkpoints

gimp_list_checkpoints
Read-only

Lists checkpoints for a specified GIMP image, oldest first, so you can review available restore points before undoing or comparing edits.

Instructions

Checkpoints of an image, oldest first.

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_list_checkpoints"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
imageYes
checkpointsYesOldest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered externally. The description adds one genuine behavioral fact the annotations do not: results are ordered oldest first. It says nothing about result volume, whether checkpoints include layers/undo state, or what happens with an unknown image id.

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

Conciseness4/5

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

Seven words, front-loaded, with no filler or repetition — the ordering detail is placed where it is immediately visible. It is terse to the point of under-specification, but nothing in it is wasted.

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?

An output schema exists, so return values need not be described, and annotations cover the read-only nature. However, for a tool in a checkpoint lifecycle (create/list/restore/delete), the description leaves the agent to infer the purpose of listing checkpoints and any relation to gimp_restore_checkpoint, leaving a visible gap.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains that 'image' is an id from gimp_status. The description adds no further meaning about the parameter, which is expected given the baseline for fully documented schemas.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase names the resource (checkpoints of an image) and the ordering (oldest first), but is a noun fragment with no verb — the 'list' action is inferred from the tool name rather than stated. It does implicitly separate it from gimp_create_checkpoint, gimp_delete_checkpoint and gimp_restore_checkpoint by describing a retrieval of existing checkpoints.

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?

There is no statement of when to call this versus siblings such as gimp_restore_checkpoint, gimp_delete_checkpoint, or gimp_inspect_image. An agent gets no cue about the workflow (e.g., list checkpoints to find an id before restoring) or any precondition beyond the required image parameter.

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