Skip to main content
Glama
Sign In
gimp-mcp

gimp-mcp

by mhbxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

GIMP status

gimp_status
Read-only

Diagnoses the connection to a running GIMP session by returning its version, session ID, and open image IDs, letting you confirm readiness before editing.

Instructions

Diagnose the connection to the running GIMP session: GIMP version, session id and the list of open images (with their ids). Call this first.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
imagesYes
socketYes
connectedYes
session_idYesChanges whenever GIMP restarts; ids from older sessions are rejected.
gimp_versionYes
plugin_versionYesVersion of the GIMP plug-in (must share MAJOR.MINOR).
server_versionYesVersion of this MCP server.
bridge_protocolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.6.0
    • addedOutput schema / properties / plugin_version
      Added value: +{
+  "description": "Version of the GIMP plug-in (must share MAJOR.MINOR).",
+  "title": "Plugin Version",
+  "type": "string"
+}
    • addedOutput schema / properties / server_version
      Added value: +{
+  "description": "Version of this MCP server.",
+  "title": "Server Version",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "connected",
-  "gimp_version",
-  "session_id",
-  "bridge_protocol",
-  "socket",
-  "images"
-]New value: +[
+  "connected",
+  "gimp_version",
+  "session_id",
+  "bridge_protocol",
+  "server_version",
+  "plugin_version",
+  "socket",
+  "images"
+]
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe local read. The description adds the diagnostic framing and the fact that open images are enumerated, but the concrete return payload is also covered by the output schema, so the extra behavioral insight is modest. Nothing contradicts the annotations.

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 short sentences, front-loaded with the purpose and closed with the ordering instruction; every clause carries information. There is no filler or restatement of the tool name.

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

Completeness5/5

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

For a zero-parameter, read-only status tool with an output schema documenting return values and annotations covering the safety profile, the description supplies everything an agent needs: what it reports and when to call it. Nothing material is missing.

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?

The tool takes no parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description is needed to clarify argument usage.

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 pairs a specific verb ("Diagnose the connection") with a specific resource (the running GIMP session) and enumerates what is returned: GIMP version, session id, and open image ids. This clearly separates it from siblings like gimp_inspect_image or gimp_inspect_item, which inspect content rather than verify connectivity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Call this first" gives explicit ordering guidance, which is the key usage decision for a session-bootstrap tool. There is no statement of when not to use it or of alternatives, but for a zero-parameter diagnostic that acts as an entry point, that gap is minor.

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