Skip to main content
Glama
Sign In
genart-dev

genart-mcp

by genart-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

design_add_bridge

Adds a bridge silhouette layer spanning terrain elements, with arch, suspension, footbridge, and flat crossing styles plus preset options for generative scenes.

Instructions

Add a bridge silhouette layer spanning between terrain elements. Supports arch, suspension, footbridge, and flat crossing styles. Presets: stone-arch, wooden-footbridge, suspension-bridge, flat-crossing.

Input Schema

NameRequiredDescriptionDefault
nameNoCustom layer name.
seedNoRandom seed for bridge variation.
spanNoBridge span as fraction of canvas width (0.15-0.8).
colorNoBridge structure color as hex.
presetNoBridge preset. Defaults to 'stone-arch'.
deckColorNoBridge deck color as hex.
depthLaneNoDepth lane placement. Defaults to 'midground'.
xPositionNoHorizontal center position 0-1.
yPositionNoVertical position 0.2-0.9.
bridgeStyleNoBridge style.
atmosphericModeNoAtmospheric depth mode.

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 the minimum by identifying that this creates an additive silhouette layer and by listing supported styles/presets. It does not disclose side effects, whether the operation is non-destructive, how layer ordering is affected, or what the tool returns.

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 short, front-loaded sentences with no filler. It immediately states the core action and then lists supported variants.

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

Completeness3/5

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

The schema is rich and fully described, so the description does not need to repeat parameter details. However, for an 11-parameter mutation-style layer tool with no annotations and no output schema, the description is thin on behavioral context and does not explain how it interacts with existing terrain or layers.

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 11 parameters are already documented with ranges, defaults, and enums. The description reinforces the style and preset enums but adds little parameter meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: it adds a 'bridge silhouette layer' that spans between terrain elements. It also states supported styles and presets, which makes the tool's role clear against 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 Guidelines3/5

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

Usage is implied by 'spanning between terrain elements,' suggesting this is for bridge placement in a landscape scene, but there is no explicit when-to-use guidance or routing versus siblings such as design_add_boat, design_add_fence, or design_add_building.

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