Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

add_zones

Add multiple garden zones in one call and get their IDs, avoiding repeated single-zone requests. Define type, shape, and position for functional, planting, and infrastructure areas.

Instructions

Add multiple zones in a single call. Returns array of zone IDs. Use this instead of calling add_zone multiple times.

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": {
      "zones": "<zones>"
    },
    "name": "add_zones"
  }
}

Input Schema

NameRequiredDescriptionDefault
zonesYesArray of zone specifications

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does meaningful work: it discloses the return shape (array of zone IDs, implying result order matches input order) and supplies per-type default heights that the schema only alludes to with "default varies by type". It stops short of describing atomicity/partial-failure behavior or overlap and locking consequences, which matter for a mutation tool.

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 the purpose, batching advice, and return value in two short sentences before the reference table. The 14-row type list is long but scannable and information-dense; it partially duplicates the get_zone_types sibling, which is the only real waste.

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?

For a single nested-batch parameter with a fully documented schema and no output schema, the description closes the main remaining gaps: return value, batching rationale, and per-type defaults. Remaining omissions (units/coordinate system, failure semantics) are either covered by sibling tools or the schema's own parameter text.

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; the description earns a bump by annotating every zoneType enum value with a plain-language meaning, a default elevation, and a functional/planting/infrastructure category, none of which the bare enum conveys. It adds nothing about the geometry parameters (x/y/width/height/polygon/path), but those are already richly documented in the schema.

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?

Names a specific verb and resource ("Add multiple zones in a single call") and explicitly distinguishes itself from the singular sibling add_zone. An agent can pick between add_zone and add_zones from the description alone.

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?

Gives an explicit routing rule: use this instead of calling add_zone multiple times. It does not spell out the inverse case (use add_zone for a single zone) or note prerequisites such as needing a created/saved garden, but the intent is unambiguous.

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