Skip to main content
Glama
gimp-mcp-studio
by Onru-Labs

invert_colors

Invert all colors in a target GIMP layer to create a negative, optionally specifying the image index and layer name.

Instructions

Invert all colors in a layer (create a negative).

Parameters:

  • image_index: Target image index (default 0)

  • layer_name: Layer to invert; defaults to active layer

Returns status dict.

Input Schema

NameRequiredDescriptionDefault
layer_nameNo
image_indexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It says the tool transforms layer colors but never states whether the change is in-place and destructive, whether it is undoable, or whether it applies to the whole layer versus a selection; only 'Returns status dict' hints at output.

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?

The one-line purpose is front-loaded, followed by a compact parameter list, with no filler sentences. Minor redundancy in repeating defaults the schema already encodes, but overall tight and scannable.

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?

For a simple two-parameter, no-annotation tool the description covers purpose, both parameters, and the return shape. It falls short on mutation semantics — in-place versus non-destructive, undo behavior, and layer-versus-selection scope — which matter for a color-modifying operation.

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 description coverage is 0%, so the description must compensate, and it does: it documents both parameters and, crucially, explains that a null layer_name resolves to the active layer — meaning the schema does not convey on its own. The image_index default of 0 is restated but not given further meaning.

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 states a specific verb and resource ('Invert all colors in a layer') and clarifies the effect with '(create a negative)'. It is clearly distinct from siblings like desaturate or adjust_curves, though it does not explicitly differentiate itself from invert_selection.

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 guidance, no mention of when to prefer this over invert_selection or the adjustment tools, and no prerequisites stated. The only contextual hint is the default-to-active-layer note, which is parameter behavior rather than usage routing.

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