WorldPainter MCP

Overview Schema Source Related Servers Discussions Admin

wp_plan_terrain_edit

Create a non-writing edit plan for WorldPainter projects, specifying height and paint operations with regions and masks, then preview before saving.

Instructions

Create a non-writing edit plan.

Height operation types: smooth(radius,passes,strength), erosion(iterations,talus,strength), ridge_valley(radius,scale,strength), raise_lower(delta,strength), slope_limit(max_slope,iterations,strength), coastline_soften(sea_level,width,radius,strength). Paint operation types: terrain(terrain), layer(layer,value), biome(biome_id), plants(layer, plants=[{name,weight}], density=0.25,seed=1), water(data_path): NPZ with equal 1D arrays x,y (absolute integer world coordinates), bed (float ground height), water (integer water level). Only lowers existing ground. Water does not clear plants or change terrain/biomes; add masked layer/terrain/biome operations. Plants creates a NEW native Custom Plants layer, with valid-block checks and no farmland. Each paint operation may have its own mask_path, intersected with the global mask. Use wp_get_world_info to see existing layer names; plants must use a new name. Region types: rectangle(x,y,width,height,feather), circle(center_x,center_y,radius,feather), or polygon(points,feather). mask_path may point to a grayscale image covering the full dimension. This tool never saves a .world file; preview is mandatory next.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`region`	No
`dimension`	No
`mask_path`	No
`world_path`	Yes
`paint_operations`	No
`height_operations`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 3, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it states the tool never saves a .world file, that preview is mandatory next, that water only lowers existing ground and does not clear plants or change terrain/biomes, that plants creates a new native layer with valid-block checks and no farmland, and that per-operation masks are intersected with the global mask.

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?

Front-loads the core purpose in one sentence, then organizes details by height operations, paint operations, region types, and masking. Despite its length, every sentence conveys necessary semantic or behavioral information for this complex tool.

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

Completeness5/5

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

Given the tool's complexity, the presence of an output schema (so return values need not be explained), and the absence of annotations, the description is complete enough for an agent to construct a valid plan. It covers operation schemas, masking, region formats, and the mandatory preview handoff, leaving only the minor dimension parameter unaddressed.

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 0%, so the description must compensate. It thoroughly documents the shape of paint_operations and height_operations (with field names and defaults), region types (rectangle, circle, polygon with their fields), and mask_path behavior. It does not explain world_path or dimension, though world_path is largely self-evident.

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+resource: 'Create a non-writing edit plan,' then details the operation types the plan supports. It names wp_get_world_info for layer names and says preview is mandatory next, which routes the agent, but it does not explicitly contrast with wp_apply_terrain_plan or wp_analyze_terrain.

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

Usage Guidelines4/5

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

Provides clear workflow context: use wp_get_world_info to see existing layer names, and preview is mandatory next. It implies this is the planning step before preview/apply, but does not explicitly state when to choose this over wp_analyze_terrain or other read tools.

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

Deploy Server