Skip to main content
Glama
Sign In
genart-dev

genart-mcp

by genart-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

design_add_bristle_dab

Add a bristle-dab layer of impressionist short dabs grid-placed over a vector field to create stippled, hatched, or painterly impasto effects in generative art.

Instructions

Add a bristle-dab layer — impressionist short dabs grid-placed over a vector field. Creates stippled, hatched, and painterly impasto effects.

Input Schema

NameRequiredDescriptionDefault
seedNoRandom seed for reproducible output (default: 0).
fieldNoVector field shorthand: "noise:seed:scale:octaves", "linear:angleDeg:magnitude", "radial:cx:cy:diverge|converge", "vortex:cx:cy:radius", "algorithm:channelName". Default: "noise:0:0.1:3".
indexNoLayer stack position (default: top).
taperNoBrush tip taper style (default: pointed).
colorsNoJSON array of hex color strings (default: ["#3a2a1a","#6b4c2a"]).
opacityNoLayer opacity 0–1 (default: 0.65).
textureNoSurface texture preset (default: smooth).
wetnessNoPaint wetness 0–1 for wet-on-wet mixing (default: 0 = dry).
colorModeNoBristle color distribution mode (default: single).
dabLengthNoLength of each dab in pixels (4–100, default: 20).
paintModeNoComposite operation (default: normal).
brushWidthNoBrush width in pixels (4–120, default: 24).
lightAngleNoLight direction in degrees 0–360 (default: 315 = upper-left).
mixStrengthNoWet mixing strength 0–1 (default: 0.5).
shadowDepthNoShadow darkness 0–1 (default: 0.3).
bristleCountNoNumber of bristles per dab (4–40, default: 12).
lightElevationNoLight elevation 0–1, 0=raking shadows, 1=overhead (default: 0.5).
overlapDensityNoGrid density relative to brush width — higher = more overlap (0.1–2.0, default: 0.6).
atmosphereHorizonNoHorizon Y position 0–1 (default: 0.5).
highlightStrengthNoSpecular highlight strength 0–1 (default: 0.25).
shadowTemperatureNoShadow color temperature -1 (cool/blue) to +1 (warm/orange) (default: 0).
atmosphereStrengthNoAtmospheric perspective strength 0–1 (default: 0 = disabled).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It says the tool adds a layer and produces dab effects, but it does not disclose side effects, whether an existing vector field is required, how layer insertion works, or what the operation returns. For a complex 22-parameter mutation tool, this leaves significant behavioral gaps.

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 compact and front-loaded: it first states the action and mechanism, then lists representative effects. Both sentences earn their place without redundant filler.

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?

The tool has 22 optional parameters, no annotations, and no output schema. The description explains the basic purpose but not enough about usage context, dependencies, layer-stack behavior, or expected results for an agent to confidently invoke such a complex operation.

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 the parameter meanings are already fully documented in the schema. The description does not add any parameter-specific semantics beyond the schema, so the baseline score of 3 is appropriate.

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: adding a bristle-dab layer. It also explains the mechanism (grid-placed short dabs over a vector field) and visual effects, making the tool understandable. It does not explicitly distinguish this from nearby siblings such as design_add_bristle_stroke or design_brush_stroke.

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?

The description mentions visual outcomes like stippled, hatched, and impasto effects, but gives no explicit when-to-use guidance or comparison to alternative brush/stroke tools. An agent must infer that this is for impressionist dab-based texture rather than other painting or mark-field tools.

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

Deploy Server

Other Tools