Skip to main content
Glama
Sign In
gimp-mcp

gimp-mcp

by mhbxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Save project (XCF)

gimp_save_image
Destructive

Save an image as a GIMP project (.xcf) while preserving layers, groups, masks, and text; write to the current file or a specified path with overwrite control.

Instructions

Save the image as a GIMP project (.xcf), keeping layers, groups, masks and text. Without path, saves to the image's current XCF file (a normal 'Save'). With a path, an existing file is only replaced when overwrite=true. Marks the image as having no unsaved changes.

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

Input Schema

NameRequiredDescriptionDefault
pathNoAbsolute .xcf path; default: current XCF file.
imageYesImage id from gimp_status, e.g. 'image:1@a1b2c3d4'.
overwriteNo

Output Schema

NameRequiredDescriptionDefault
bytesYesSize of the written file.
dirtyYes
imageYes
xcf_fileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag this as a destructive, non-read-only, closed-world write. The description goes beyond them by disclosing the overwrite guard (existing files are only replaced when overwrite=true) and the side effect that the image is marked as having no unsaved changes — a state change annotations alone would not reveal.

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 tight sentences, front-loaded with what is saved, then mode behavior, then the state side effect. Every clause carries information an agent needs; no restating of the title or name.

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 so return values need not be explained, and the description covers the mutation semantics, the overwrite risk, and the dirty-flag side effect. It does not state what happens when a path is supplied to an existing file with overwrite=false (error vs. silent no-op), the one behavioral gap remaining.

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

Parameters4/5

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

Schema coverage is 67% and 'overwrite' has no schema description; the prose supplies its exact semantics, plus the default behavior when path is omitted. The image id parameter is already fully documented in the schema, so the added value is concentrated where documentation was thin.

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 names a specific verb and resource ('Save the image as a GIMP project (.xcf)') and enumerates what is preserved (layers, groups, masks, text), which implicitly separates it from gimp_export_image. It never names the export sibling explicitly, so an agent must infer that flattening/other formats belong elsewhere.

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?

It usefully distinguishes the two modes: no path is 'a normal Save', a path requires overwrite=true to replace an existing file. However, there is no guidance on when to choose this over gimp_export_image for non-XCF output, which is the most likely sibling confusion in this toolset.

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