Skip to main content
Glama
Sign In
gimp-mcp

gimp-mcp

by mhbxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Select all / none / invert

gimp_modify_selection

Modify a GIMP image selection by selecting the entire canvas, clearing the selection, or inverting it using an image ID and action.

Instructions

'all' selects the whole canvas, 'none' clears the selection, 'invert' inverts it.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
emptyYes
imageYes
boundsYesBounding box of the selection, clipped to the canvas; null when empty.
containsNoWhether (probe_x, probe_y) is selected (> 50%), when a probe point was given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false; the description adds no behavioral context beyond that, saying nothing about whether the prior selection is recoverable, whether an undo step is created, or what effects clearing has on subsequent operations. The phrase 'none clears the selection' is a mild behavioral cue but is just the enum semantics restated.

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?

A single front-loaded sentence covering all three cases with no filler or repetition, which is the right size for a three-value enum tool.

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?

The tool is simple, has an output schema so return values need no explanation, and the action semantics are fully covered. However, the description gives no context on the sibling alternatives for selection creation, and the image prerequisite is left entirely to the schema, leaving a small but real completeness gap.

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 50% because the action enum carries no per-value descriptions; the description fills exactly that gap by defining each allowed action value, which is genuinely additive. The image parameter's meaning is already fully documented in the schema ('Image id from gimp_status'), so nothing further is needed there.

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 quoted text maps each of the three actions to a concrete effect ('all' selects the whole canvas, 'none' clears, 'invert' inverts), so an agent can tell exactly what the tool does with the required action argument. It does not differentiate from siblings like gimp_select_rectangle, gimp_select_ellipse, or gimp_get_selection, keeping it at 4 rather than 5.

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 when-to-use or when-not-to-use guidance. The description never says how this differs from gimp_select_rectangle/gimp_select_ellipse (which create shaped selections) or gimp_get_selection (which reads the current selection), so the agent must infer routing from names alone.

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