Place stairs, columns, pergolas, pots and house plants (place_presets): a home3dplan MCP tool

What it does

Place preset pieces at scene positions in metres on a storey (x = plan x / 1000, z = minus plan y / 1000). Kinds: stairs (the position is the FOOT of the flight and the flight runs toward +z, down the plan, unless rotation turns it, so a stair against the south wall needs rotation 180; it rises to the storey above unless toFloor says otherwise; its recipe can set totalRise, treadDepth, targetRiser, landingDepth and width in mm), column, pergola, pottery, houseplant. Preset names from list_presets; a unique part of a name also works. Each piece seats on the storey’s floor unless surfaceY (metres) says otherwise (a pot on a table).

A write. It saves one revision of the project, which appears in the open editor at once and can be undone there. Scope: **projects:write**.

Inputs

**projectId** (string, required): See the tool’s description.

**floor** (integer): Default 0.

**items** (({ kind: stairs | column | pergola | pottery | houseplant, preset: string, x: number, z: number, rotation?: number, surfaceY?: number, toFloor?: integer | null, recipe?: object })[], required): See the tool’s description.

What comes back

What changed, in words and in a structured form, and the link that opens the project in the editor on the right storey and view.

Tip: if the project changed in the editor between two calls, the write is refused as a conflict and the assistant opens the project again. Nothing is overwritten.

Ask for it like this

"Use place_presets on my project."

The assistant chooses the tool and fills its inputs from what you said; you do not name the tool or type its inputs.

Read next

• Search the catalogue
• Place furniture
• Add site elements