Skip to main content
Glama

gimp_draw

Draw a stroke through image coordinates using a chosen GIMP tool, with optional closed path, color, size, opacity, layer, and image.

Instructions

Pinta un trazo que pasa por points=[x1,y1,x2,y2,...] (coordenadas de imagen) con la herramienta indicada. closed=True cierra el trazo volviendo al primer punto.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNo
toolNopaintbrush
colorNo
closedNo
pointsYes
opacityNo
image_idNo
layer_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds the useful 'closed=True returns to the first point' behavior, but says nothing about which layer/image is mutated by default, undo implications, or whether color/opacity/size come from current context.

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 tight sentences; the point-format explanation is front-loaded and the closed behavior follows. Nothing is wasted, though the language does not match the surrounding English toolset.

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

Completeness3/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 core geometry is described. However, for an 8-parameter mutation tool with zero schema documentation, the omission of layer/image target defaults and the drawing attribute parameters leaves real gaps.

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 0% across 8 parameters, so the description carries the burden. It does document the two most critical semantics: the flat x1,y1,x2,y2 point format and closed=True. Size, color, opacity, image_id, and layer_id remain completely undefined in both description and schema.

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+resource ('pinta un trazo') plus the geometry model (points list in image coordinates), which separates it from siblings like gimp_fill or gimp_gradient. It does not explicitly name what it is not, so it stops short of a 5.

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 when-to-use, when-not-to-use, or alternative is given. An agent must infer that this is for freehand/polyline painting rather than selection stroking (gimp_stroke_selection) or filling (gimp_fill).

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