Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

add_zone

Create a new garden zone by type and define its shape, position, or path; returns the zone ID for further layout and design work.

Instructions

Add a new zone to the garden. Returns the zone ID.

Available zone types (type → default height → category): • entry — 0.3m — functional (entrance area) • relaxation — 0.5m — functional (seating, lounging) • activity — 0.3m — functional (play, sports) • utility — 0.4m — functional (compost, storage, bins) • wild — 0.6m — functional (naturalistic area) • tall_plants — 2.0m — planting (trees, large shrubs) • privacy_screen — 1.8m — planting (hedges, screening) • low_plants — 0.5m — planting (perennials, groundcover) • herbs — 0.3m — planting (herb garden) • lawn — 0.05m — planting (grass area) • path — 0.05m — infrastructure (walkways) • building — 3.0m — infrastructure (structures) • terrace — 0.2m — infrastructure (paved patio) • parking — 0.05m — infrastructure (driveway, car space)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "zoneType": "<zoneType>"
    },
    "name": "add_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoRectangle centre X (metres by default)
yNoRectangle centre Y (metres by default)
pathNoCorridor along a centreline: absolute waypoints (metres) and corridor width. Replaces x/y/width/height/points.
labelNoOptional: Custom label for the zone
notesNoOptional: Design notes — why this zone was placed here, constraints, alternatives considered
widthNoRectangle width (plan size, not height)
heightNoRectangle depth on the plan (NOT vertical height — that is `elevation`)
lockedNoOptional: lock the zone (existing features the design must not change — paving, sheds, existing hedges). Locked zones are flagged when other zones overlap them.
pointsNoWith x/y: polygon vertices as offsets from (x, y). Prefer `polygon` (absolute) instead.
polygonNoAbsolute polygon vertices in metres (garden coordinates). Replaces x/y/width/height/points.
zoneTypeYesType of zone to create
elevationNoOptional: vertical height of the zone prism in metres (default varies by type)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the return value (zone ID), but says nothing about whether geometry modes are mutually exclusive (only the schema hints at this), which coordinate system or units are assumed, whether overlaps are permitted, or whether the operation is reversible via `undo`.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and return value, then a compact reference table. The table is long but each row carries information (default height, category) not present in the enum, so the length is earned; the bullet list could have been wrapped in a short lead-in sentence explaining its connection to `elevation`.

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?

For a 12-parameter tool with nested objects and alternative geometry representations, the definition covers what a zone type means and what is returned. It is still silent on the coordinate-system/units assumption and on the single-vs-batch relationship with `add_zones`, which are the most likely sources of a mis-call.

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 coverage is 100%, so the baseline is 3, and the zone-type table genuinely adds meaning beyond the enum: it supplies default heights and categories that the `elevation` parameter only gestures at ('default varies by type'). The description thus resolves a real ambiguity in the schema.

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 and resource ('Add a new zone to the garden') plus the return value ('Returns the zone ID'). It does not distinguish itself from the sibling `add_zones` (batch creation), so an agent cannot tell from the description alone which one to pick.

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?

No when-to-use or when-not-to-use guidance is given, and no prerequisites are stated. The sibling list contains `add_zones`, `update_zone`, and `get_zone_types`, and the description never says when to use this singular tool over the batch variant or when a zone should be modified rather than created.

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