genart-mcp

design_paint_layer

Add a painting layer shaped by a 2D vector field, with watercolor, oil, gouache, ink, pastel, or charcoal media for generative artwork.

Instructions

Add a painting layer driven by a 2D vector field. Supports watercolor, oil, gouache, ink, pastel, and charcoal media.

Input Schema

Name	Required	Description
`seed`	No	Random seed (default: 0).
`debug`	No	Show vector field debug overlay (default: false).
`field`	No	Vector field shorthand or JSON. Shorthands: "noise:seed:scale:octaves", "linear:angleDeg:magnitude", "radial:cx:cy:diverge\|converge", "vortex:cx:cy:radius", "algorithm:channelName" (reads from algorithm data bridge). Defaults to "noise:0:0.1:3".
`grain`	No	Paper grain / texture intensity 0–1 (charcoal, gouache, pastel).
`index`	No	Layer stack position (default: top).
`smear`	No	Blend charcoal marks broadly (charcoal only, default: false).
`style`	No	Ink stroke style (ink only, default: fluid).
`taper`	No	Stroke taper (ink only, default: none).
`colors`	No	Array of hex colors, e.g. ["#4a7fb5", "#7ab8d4"].
`medium`	Yes	Painting medium.
`weight`	No	Stroke weight in pixels (ink only, default: 2).
`buildup`	No	Mark density buildup 0–1 (pastel only, default: 0.5).
`density`	No	Mark density 0–1 (charcoal only, default: 0.5).
`impasto`	No	Raised paint bevel effect (oil only, default: false).
`opacity`	No	Layer opacity 0–1 (default: 1.0).
`scumble`	No	Dry-brush scumble gaps (oil only, default: false).
`dilution`	No	Water dilution 0–1 (watercolor only, default: 0.5).
`dryBrush`	No	Dry-brush texture (gouache only, default: false).
`softness`	No	Mark softness / smear 0–1 (pastel only, default: 0.6).
`debugMode`	No	Debug overlay mode (default: "all").
`edgeStyle`	No	Edge style (watercolor only, default: soft).
`fieldCols`	No	Field grid columns (default: 20).
`fieldRows`	No	Field grid rows (default: 20).
`blendRadius`	No	Wet paint drag/blend distance in pixels (oil only, default: 8).
`granulation`	No	Pigment granulation 0–1 (watercolor only, default: 0.3).
`debugOpacity`	No	Debug overlay opacity 0–1 (default: 0.7).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Nov 2, 2026

TDQS

C2.9/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. 'Add' implies a mutation, but the description does not disclose side effects, required context, whether it creates a new layer in the stack, permissions, or what happens to existing layers.

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?

The description is two sentences with no wasted words, and the primary action is front-loaded before the supported media list.

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 26-parameter mutation tool with no annotations and no output schema needs more context than this. The description does not explain layer creation behavior, interaction with the vector field, or how it relates to the large set of sibling layer and field tools.

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 100%, so all 26 parameters are already documented in the schema. The description only restates the medium enum in prose and adds no meaningful semantics beyond structured fields.

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?

The description states a specific verb and resource: 'Add a painting layer driven by a 2D vector field,' and names the supported media. It is distinguishable from a generic add-layer tool by the vector-field mechanism, though it does not explicitly contrast with siblings such as design_add_layer or design_add_mark_field.

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 guidance on when to use this tool versus the many related painting/layer/field tools, nor any prerequisites such as needing an open sketch or an existing vector field. The media list describes capabilities, not usage conditions.

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

Deploy Server

design_paint_layer

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools