Skip to main content
Glama
Sign In
genart-dev

genart-mcp

by genart-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

design_add_boat

Add a boat or ship silhouette layer to water scenes, choosing sailboat, rowboat, fishing boat, or cargo ship presets with position, scale, tilt, and color controls.

Instructions

Add a boat or ship silhouette layer on water. Renders sailboats, rowboats, fishing boats, or cargo ships. Presets: sailboat, rowboat, fishing-boat, cargo-ship.

Input Schema

NameRequiredDescriptionDefault
nameNoCustom layer name.
seedNoRandom seed for boat variation.
tiltNoWave rocking tilt in degrees -15 to 15.
colorNoHull color as hex.
scaleNoScale factor 0.02-0.15.
presetNoBoat preset. Defaults to 'sailboat'.
boatTypeNoBoat form type.
depthLaneNoDepth lane placement. Defaults to 'midground'.
sailColorNoSail/cabin color as hex.
xPositionNoHorizontal position 0-1.
yPositionNoVertical position 0.2-0.9.
atmosphericModeNoAtmospheric depth mode.

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?

No annotations are provided, so the description carries the full behavioral burden. It says this adds a layer, but omits whether the layer is added to the active sketch, how ordering works, what defaults apply, and whether changes are reversible.

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?

Three short sentences, front-loaded with the action and resource, with no wasted text. The preset sentence is redundant with the schema but remains compact and scannable.

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?

This is a 12-parameter layer-creation tool with no annotations and no output schema. The description explains what is added, but not the mutation context, defaults, layer interaction, or visual behavior needed for confident invocation.

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 baseline is 3. The description repeats the preset values already present in the schema and does not add further meaning for options such as seed, tilt, color, scale, or position.

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 boat or ship silhouette layer, with water context and enumerated boat forms. It is clear, but it does not explicitly differentiate itself from neighboring landscape-layer tools.

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 phrase 'on water' implies a water-scene context, but there is no explicit guidance on when to use this tool, when not to, or which sibling tool to choose instead.

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