Skip to main content
Glama
Sign In
gimp-mcp

gimp-mcp

by abelduarte
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gimp.get_image_bitmap

Retrieve a GIMP image as MCP content, optionally scaling to max dimensions or cropping a specific region before output.

Instructions

Return a GIMP image as MCP image content with optional max-size scaling and region extraction.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gimp.get_image_bitmap"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_idNoOptional image ID. Defaults to the first open image.
max_widthNoOptional maximum output width.
max_heightNoOptional maximum output height.
regionNoOptional crop region before scaling.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior but fails to mention default behavior for image_id (first open image), what happens if no region is specified, or the output format (e.g., PNG). It does not state if the operation is destructive or requires permissions.

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 a single, well-structured sentence of 16 words. It front-loads the key action and optional features without redundancy.

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

Completeness2/5

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

The tool has 0 required parameters and a complex optional region object, yet the description omits default behavior for max_width/max_height (unbounded?), the exact return format (MCP image content is vague), and potential error cases. An output schema is absent, so the description should clarify what the agent receives.

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

Parameters3/5

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

Schema coverage is 100%, but the description adds minimal value beyond the schema. The region subparameters ('origin_x', 'x', etc.) are not explained, leaving ambiguity. Baseline 3 is appropriate as the schema provides basic descriptions, but the tool's complexity demands more.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Return'), the resource ('GIMP image as MCP image content'), and optional features ('max-size scaling and region extraction'). This differentiates it from siblings like gimp.get_image, which likely returns metadata or raw data.

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 is provided on when to use this tool versus alternatives (e.g., gimp.get_image or gimp.export). The description gives no context for choosing scaling or region extraction.

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