Skip to main content
Glama

gimp_convert_mode

Convert an image's color mode between RGB, grayscale, and indexed, specifying the palette size for indexed mode.

Instructions

Convierte el modo de color de la imagen. Para indexed, colors = nº de colores de la paleta.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
colorsNo
image_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the agent knows this is a non-destructive write. However, the description adds nothing beyond that: it does not disclose that converting RGB to grayscale or indexed can permanently discard color information, nor whether the change is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core action front-loaded and no wasted words. Efficient, though extremely terse given the tool's complexity.

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?

A mutation tool with no output schema, 0% schema coverage, and an unexplained image_id parameter. It omits the key behavioral fact that mode conversion can lose color data, leaving an agent under-informed for a write operation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden, but it only explains the `colors` parameter ('Para indexed, colors = nº de colores de la paleta'). The `image_id` parameter is entirely undocumented, and `mode` relies solely on its enum values.

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?

States a specific verb and resource: 'Convierte el modo de color de la imagen' (converts the image's color mode). An agent can distinguish this from siblings like gimp_adjust or gimp_set_colors, though no sibling is named explicitly.

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?

Provides no when-to-use guidance, no prerequisites, and no mention of alternatives among the many siblings that touch image properties. The single sentence about indexed colors is a parameter hint, not usage direction.

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