Skip to main content
Glama

gimp_duplicate_layer

Duplicate a GIMP layer so the copy sits directly above the original, with an optional new name.

Instructions

Duplica una capa (queda justo encima de la original).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
layer_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds the placement behavior (duplicate sits directly above the original), but says nothing about the created layer's default naming, whether the original is untouched, or what is returned.

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?

A single short sentence with the core action front-loaded and the placement detail in parentheses; nothing is wasted. It is arguably too terse for a tool with an undocumented parameter, but structurally it is efficient.

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?

With no output schema and no annotation-derived detail, the description should tell the agent what the duplicated layer is called, whether it becomes selected, and what the call returns. None of that is present, so the definition is not sufficient on its own.

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 carries the full burden, yet it explains neither the required layer_id (which layer is targeted) nor the optional name parameter (does it rename the duplicate?). This leaves the second parameter's meaning entirely undocumented.

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 ('Duplica una capa') and adds the placement result, so the agent knows exactly what operation runs. It does not explicitly differentiate from close siblings like gimp_new_layer or gimp_duplicate_image, but the verb is unambiguous.

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?

There is no guidance on when to duplicate versus creating a new layer or copying via other means, and no prerequisites or context conditions are given. Usage must be inferred from the tool name alone.

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