Skip to main content
Glama
Sign In
gimp-mcp

gimp-mcp

by mhbxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Enable toolsets

gimp_enable_toolsets

Adds selected GIMP toolset tools to the current session’s tool list and notifies the client of the change; clients that do not refresh must restart with the toolsets enabled.

Instructions

Add the tools of one or more toolsets (see gimp_list_toolsets) to your tool list for this session. The server notifies the client that its tool list changed; a client that does not refresh its tool list needs a restart with the toolsets in --toolsets or GIMP_MCP_TOOLSETS.

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": {
      "toolsets": "<toolsets>"
    },
    "name": "gimp_enable_toolsets"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolsetsYesToolset names.

Output Schema

NameRequiredDescriptionDefault
enabledYesToolsets enabled now.
added_toolsYesTools added to the tool list by this call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.6/5.0
Behavior5/5

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

The annotations only mark this as a non-read-only, non-destructive, closed-world mutation. The description goes well beyond that by disclosing that the effect is scoped to this session, that the server sends a tool-list-changed notification, and that stale clients may require a restart with --toolsets or GIMP_MCP_TOOLSETS. Those are exactly the behavioral caveats an agent cannot infer from structured fields.

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 sentences, front-loaded with the action and followed by the operational caveat. Every clause carries information: scope, notification behavior, and the client-restart workaround.

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?

An output schema exists, so return values need no explanation, and the description covers session scope and client-refresh behavior adequately for a one-parameter tool. The only omission is what happens on repeated calls or invalid toolset names, which would matter for error handling.

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 coverage is already 100% for the single required array parameter, so the baseline is 3. The description adds meaning by defining the values as toolset names sourced from gimp_list_toolsets and clarifying that multiple entries may be supplied.

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?

States a specific verb and resource: it adds the tools of one or more toolsets to the session's tool list. It also names the sibling that supplies the valid values (gimp_list_toolsets), so an agent can immediately tell this apart from the listing tool.

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?

Guidance is clear: use it when you need tools from other toolsets, and call gimp_list_toolsets first to get names. It also gives the fallback path when a client does not refresh. It does not explicitly say when not to use it or whether repeated calls are harmless, which keeps it just short of a 5.

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