Skip to main content
Glama

Agregar forma

ps_add_shape

Create vector shapes in Photoshop (rectangle, ellipse, polygon, star, line, path) with solid or gradient fills, strokes, effects, blend modes, and opacity.

Instructions

Crea una forma vectorial: rectangle, roundRect (radius número, [tl,tr,br,bl] o 'pill'), ellipse, circle, polygon, star, line o path (points). Relleno sólido o degradado, trazo (ancho, alineación, guiones), efectos, mezcla y opacidad.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
x2No
y2No
docNoDocumento (nombre o índice desde 1). Por defecto el activo.
fillNonull/'none' = sin relleno (solo trazo)
nameNo
aboveNoCapa: nombre, 'Grupo/Capa', id numérico o {id|name|path|index|nth}
belowNoCapa: nombre, 'Grupo/Capa', id numérico o {id|name|path|index|nth}
blendNoModo de fusión: normal, multiply, screen, overlay, softLight, hardLight, vividLight, linearLight, pinLight, hardMix, colorDodge, linearDodge, colorBurn, linearBurn, darken, lighten, darkerColor, lighterColor, difference, exclusion, subtract, divide, hue, saturation, color, luminosity, passThrough
labelNo
shapeNo
sidesNo
widthNo
anchorNoPunto de la capa que se coloca en (x,y). Por defecto topleft
closedNo
heightNo
parentNoGrupo donde crearla
pointsNo
radiusNo
strokeNo
clippedNoMáscara de recorte sobre la capa de abajo
effectsNoEfectos de capa con el mismo esquema que ps_layer_style.effects: {dropShadow:[{color,opacity,angle,distance,size,blend}], outerGlow:{color,opacity,size,noise,blend}, innerGlow, bevelEmboss, satin, colorOverlay, gradientOverlay:{stops,angle}, stroke:{size,position,color}, recipe:'nombre', raw, clear}
opacityNo
visibleNo
rotationNo
thicknessNo
effectsModeNo
fillOpacityNoRelleno de la CAPA (no confundir con 'fill', que es el color de la forma)
innerRadiusNoEstrella: 0-1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says a vector shape is created, but does not disclose mutation side effects, required document context, layer insertion behavior, permissions, defaults, or reversibility.

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?

The description is a single dense sentence, front-loaded with the creation verb and shape types. It contains no filler, though it is quite terse for a 30-parameter tool.

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?

Given 30 parameters, no annotations, no output schema, and only 37% schema description coverage, the description is too sparse. It overviews main capabilities but leaves many parameter semantics, defaults, and return behavior unexplained.

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 description coverage is low at 37%, so the description should compensate. It usefully explains shape type options, radius formats, fill modes, stroke attributes, effects, blend, and opacity, but many parameters such as x, y, width, height, parent, anchor, visible, and rotation remain undocumented.

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 gives a specific verb and resource: 'Crea una forma vectorial' and enumerates the supported shape types. This clearly distinguishes it from sibling creation tools such as ps_add_text, ps_add_adjustment, or ps_create_layer.

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 explicit when-to-use guidance, no prerequisites, and no mention of alternatives or when another tool should be preferred. Usage is only implied by the verb 'creates'.

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