Skip to main content
Glama
Sign In
genart-dev

genart-mcp

by genart-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

design_create_pattern

Create custom repeating patterns from drawing commands and store them in the sketch for use by a patterns:custom layer via its patternId.

Instructions

Create a custom repeating pattern from drawing commands. The pattern is stored in the sketch and can be used by a patterns:custom layer via its patternId. Commands: line, circle, rect, arc, path, polygon. Max 200 commands, 10KB limit. Coordinates are in unit-cell space (0 to width/height).

Input Schema

NameRequiredDescriptionDefault
nameYesHuman-readable name for the pattern.
widthYesUnit cell width (local coordinates).
heightYesUnit cell height (local coordinates).
addLayerNoAlso add a patterns:custom layer using this pattern (default: true).
commandsYesDrawing commands array. Examples: {"type":"line","x1":0,"y1":0,"x2":20,"y2":20,"lineWidth":1}, {"type":"circle","cx":10,"cy":10,"r":5,"fill":true}, {"type":"rect","x":0,"y":0,"width":10,"height":10,"fill":true}, {"type":"arc","cx":10,"cy":10,"r":8,"startAngle":0,"endAngle":3.14}, {"type":"path","points":[{"x":0,"y":0},{"x":10,"y":5},{"x":0,"y":10}],"closed":true,"fill":true}, {"type":"polygon","points":[{"x":0,"y":0},{"x":10,"y":0},{"x":5,"y":10}],"fill":true}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description does carry the burden of disclosure and does provide meaningful constraints: the pattern is stored in the sketch, command limits are 200 commands / 10KB, and coordinates are in unit-cell space. It does not state permissions, overwrite behavior, failure conditions, or return details for this create operation.

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 begins with the action and resource, then adds storage/use context, command types, limits, and coordinate rules. Every sentence adds operational value with no repetition.

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?

For a create tool with no annotations and no output schema, the description covers the essential mechanics: what is created, how it is stored/used, valid commands, limits, and coordinate space. It still leaves some gaps around sibling selection and whether the new patternId is returned, but the schema and description together are largely sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds useful meaning beyond the schema by specifying the supported command types, the 200-command / 10KB limits, and that coordinates use unit-cell space from 0 to width/height.

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: creating a custom repeating pattern from drawing commands. It adds useful context that the pattern is stored in the sketch and referenced by a patterns:custom layer, but it does not explicitly distinguish this from siblings like design_update_pattern or design_add_pattern.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: create a custom pattern that can then be used via its patternId by a patterns:custom layer. The description does not explicitly say when to choose this versus design_update_pattern, design_add_pattern, or design_list_pattern_presets, so sibling routing remains inferred.

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