Skip to main content
Glama
derleiti

GIMP MCP

by derleiti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

selection_set

Define or alter selections in GIMP with geometric shapes and operations like add, subtract, or intersect to isolate areas for editing.

Instructions

Create/combine geometry selections or modify the current selection. Polygon points are a flat x/y list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
dxNo
dyNo
stepsNo
widthNo
actionYes
heightNo
pointsNo
radiusNo
operationNoreplace
session_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.5.0
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "none",
-  "all",
-  "invert",
-  "rectangle"
-]New value: +[
+  "none",
+  "all",
+  "invert",
+  "rectangle",
+  "ellipse",
+  "polygon",
+  "feather",
+  "grow",
+  "shrink",
+  "border",
+  "translate"
+]
    • addedInput schema / properties / dx
      Added value: +{
+  "default": 0,
+  "title": "Dx",
+  "type": "integer"
+}
    • addedInput schema / properties / dy
      Added value: +{
+  "default": 0,
+  "title": "Dy",
+  "type": "integer"
+}
    • addedInput schema / properties / operation
      Added value: +{
+  "default": "replace",
+  "enum": [
+    "replace",
+    "add",
+    "subtract",
+    "intersect"
+  ],
+  "title": "Operation",
+  "type": "string"
+}
    • addedInput schema / properties / points
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Points"
+}
    • addedInput schema / properties / radius
      Added value: +{
+  "default": 0,
+  "title": "Radius",
+  "type": "number"
+}
    • addedInput schema / properties / steps
      Added value: +{
+  "default": 0,
+  "title": "Steps",
+  "type": "integer"
+}
  2. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It mentions that it can 'modify the current selection,' which hints at mutation, but says nothing about permissions, reversibility, effect on existing selection, or side effects. The polygon note is the only extra behavioral detail.

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?

Two tight sentences, front-loaded with the core purpose. Every sentence earns its place, and there is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 12 parameters, 11 action enum values, and no annotations. The description does not explain what any action does, how operation combines selections, or what most parameters mean. Although an output schema exists and return values needn't be explained, the description is far too sparse to call this tool correctly.

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 description coverage is 0% across 12 parameters. The description clarifies only one parameter's format ('points are a flat x/y list'), leaving x, y, dx, dy, steps, width, height, radius, operation, action, and session_id entirely undocumented. This does not compensate for the severe schema 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?

The description clearly names the verb set (create/combine/modify) and the resource (geometry selections/current selection). It doesn't differentiate from any sibling tool, but that's potentially acceptable given no obvious selection-related sibling. The polygon point format note is useful.

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?

No guidance on when to use this tool versus alternatives, no prerequisites, no exclusions. It only states what it does, not when or why to choose it. An agent receives no routing help.

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