gimp-agent-mcp

Overview Schema Source Related Servers Discussions Admin

gimp_export

Export an image to a file path, using the extension to select the format and apply format-specific options like quality or compression.

Instructions

Export an image; the extension chooses the format (.png .webp .jpg .tiff .bmp .gif .xcf). options are passed to the format's export procedure, e.g. {"quality": 0.85} for JPEG (0..1), {"quality": 80, "lossless": false} for WebP, {"compression": 9} for PNG. Unknown option names return the valid list.

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_id": "<image_id>",
      "path": "<path>"
    },
    "name": "gimp_export"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`options`	No
`image_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses that the extension chooses the format and that unknown option names return the valid list. However, it does not mention overwrite behavior, side effects on existing files, or what happens on invalid paths, which leaves some behavioral ambiguity.

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 compact and front-loaded with the core purpose. Every sentence adds value, and the concrete examples clarify the options parameter without unnecessary prose.

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?

The description covers the essential invocation details: format selection, option examples, and error feedback. An output schema exists, so return values are already covered. The main missing pieces are explicit image_id semantics and file-overwrite behavior, but these do not seriously hinder correct use.

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%, but the description significantly compensates by explaining that 'path' controls format via extension and by giving format-specific examples for 'options'. 'image_id' is not described explicitly, but its meaning is reasonably inferable from the tool name and parameter name.

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 identifies the action ('Export an image') and the resource, and explains the format selection via file extension. It is specific enough to understand the tool, though it does not explicitly differentiate it from sibling tools like gimp_render.

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?

The description explains how format and options work, but it does not state when to use this tool versus alternatives or provide exclusion criteria. There is no comparison to gimp_render or other saving/rendering tools, so an agent gets little guidance on tool selection.

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