Skip to main content
Glama
Sign In
genart-dev

genart-mcp

by genart-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

design_fill_region

Creates a painting fill layer that procedurally generates hatch, crosshatch, stipple, scumble, or contour marks within a bounded region, with optional spatial shading.

Instructions

Create a painting:fill layer that procedurally generates marks (hatch, crosshatch, stipple, scumble, or contour) within a bounded region, with optional spatial shading. Use preset names as shorthand: hatch-light, hatch-medium, hatch-dense, crosshatch-light, crosshatch-dense, stipple-light, stipple-dense, scumble, contour.

Input Schema

NameRequiredDescriptionDefault
xNoLayer x position on canvas.
yNoLayer y position on canvas.
seedNoPRNG seed for deterministic generation (default: 42).
sizeNoBrush size override in pixels (default: 4).
brushNoInline custom BrushDefinition (overrides brushId). Must include 'id' and 'name'.
colorNoStroke color as hex (default: "#000000").
indexNoLayer stack position (default: top).
widthNoLayer width on canvas.
heightNoLayer height on canvas.
regionNoRegion to fill. Types: {"type":"bounds"} (default, fills layer bounds), {"type":"rect","x":N,"y":N,"width":N,"height":N}, {"type":"ellipse","cx":N,"cy":N,"rx":N,"ry":N}, {"type":"polygon","points":[{"x":N,"y":N},...]}.
brushIdNoBrush preset ID (default: "ink-pen").
layerIdNoUpdate an existing painting:fill layer. If omitted, creates a new one.
opacityNoLayer opacity 0–1 (default: 1.0).
shadingNoShading function (default: {"type":"uniform"}). Types: {"type":"linear","angle":0,"range":[0.2,1.0]}, {"type":"radial","cx":0.5,"cy":0.5,"range":[0.0,1.0]}, {"type":"noise","seed":0,"scale":1,"range":[0.3,1.0]}. cx/cy are normalised [0,1] in region space.
strategyNoFill strategy object or preset name. Preset names: hatch-light, hatch-medium, hatch-dense, crosshatch-light, crosshatch-dense, stipple-light, stipple-dense, scumble, contour. Objects: {"type":"hatch","angle":45,"spacing":8}, {"type":"crosshatch","angles":[45,135],"spacing":8,"passDecay":0.7}, {"type":"stipple","density":40,"distribution":"poisson"}, {"type":"scumble","density":15,"strokeLength":20,"curvature":0.5}, {"type":"contour","spacing":8,"smoothing":0.3}.
layerNameNoName for the new layer (default: 'Fill').
shadingAffectsNoWhich properties shading modulates (default: ["density"]).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.4/5.0
Behavior3/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 discloses that the tool creates a procedural fill layer with mark types and optional shading, but it does not state side effects, reversibility, permission needs, or what happens when updating an existing layer via layerId.

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?

Two sentences, front-loaded with the core purpose and followed by relevant preset shorthand. There is no redundant or empty phrasing.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The schema is rich and covers all parameters, so the description does not need to restate them. It gives enough context to understand the tool's role, though it could say more about when to choose this over sibling fill/paint 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 the schema already documents all 17 parameters. The description adds preset-name shorthand and names the procedural mark families, but most parameter-specific behavior is left to the 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 and resource: 'Create a painting:fill layer' with procedural mark types. This is clear, but it does not explicitly differentiate the tool from nearby fill/paint siblings such as design_update_fill or design_paint_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?

The description does not say when to use this tool instead of alternatives, nor when not to use it. The note about preset names is parameter guidance, not usage guidance for tool selection.

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