Skip to main content
Glama
Sign In
gimp-mcp

gimp-mcp

by mhbxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Brightness / contrast

gimp_brightness_contrast
Destructive

Adjust a layer's brightness and contrast from -100 to 100, with 0 leaving values unchanged. Choose destructive pixel edits or a removable GIMP filter.

Instructions

Adjust brightness and contrast of a layer, each from -100 to 100 (0 = unchanged; mapped to GIMP's -1..1). One undo step.

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": {
      "item": "<item>"
    },
    "name": "gimp_brightness_contrast"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesItem id (layer, group, mask...) e.g. 'item:5@a1b2c3d4'.
contrastNo
brightnessNo
destructiveNotrue: change the layer's pixels (respects the selection). false: add an editable GIMP filter on the layer (pixels untouched, removable, saved in XCF; applied to the whole layer).

Output Schema

NameRequiredDescriptionDefault
itemYes
filterYesId of the editable filter (non-destructive only), verified to exist.
operationYesGEGL/GIMP operation that was applied.
destructiveYesTrue when the layer's pixels were changed.
restricted_to_selectionYesTrue when only the selected area was changed.

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 declare destructiveHint=true and readOnlyHint=false. The description adds useful behavioral context beyond annotations: 'One undo step' and the -100..100 to GIMP -1..1 mapping. It does not explain the destructive-vs-filter behavior in the description, but that is covered by the schema's destructive parameter.

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?

The description is two compact sentences, front-loaded with the action and range. 'One undo step' is concise and earns its place as useful behavioral context.

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?

For a simple adjustment tool with annotations and an output schema, the definition is largely complete. Minor gaps remain: it doesn't mention that item may be a group or mask, and it doesn't discuss non-destructive behavior in the description, though both are supported or documented elsewhere.

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 50%, with item and destructive already documented. The description compensates for the undocumented brightness/contrast parameters by explaining their range, that 0 means unchanged, and the mapping to GIMP's -1..1 scale. It adds little for item/destructive, but those are already covered by the schema.

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, 'Adjust', and specific resources, 'brightness and contrast', with the target 'layer' and range. It is clear and distinguishable from siblings like gimp_hue_saturation, though it says 'layer' while the item parameter also accepts group/mask.

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?

Usage is implied by the tool name and description, but there is no explicit when-to-use or when-not-to-use guidance, nor any mention of alternatives such as gimp_hue_saturation or gimp_set_layer_properties. An agent can infer the purpose but is not routed between similar adjustment tools.

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