Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

get_zones

Retrieves every garden zone with its editor geometry and locked status so you can inspect what areas the design must not change. Use site analysis for absolute polygons and areas.

Instructions

Get all zones in the garden (editor geometry: centre + relative points; locked marks zones the design must not change). For absolute polygons and areas use get_site_analysis.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_zones"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 full burden, and it does disclose meaningful behavior: the returned geometry is editor-relative (centre + relative points) and `locked` signals zones the design must not change. The 'Get all' phrasing implies a read-only, non-mutating call. It does not mention ordering, size limits, or whether empty gardens return an empty list.

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?

Two sentences, no filler. The core purpose and return shape come first, and the sibling routing note is placed second where it belongs as a disambiguation.

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

Completeness4/5

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

With no output schema, the description must explain what comes back, and it does at a useful level of detail (relative geometry, `locked` flag). What is missing is the surrounding envelope — whether zones carry names/ids/types alongside geometry — which matters for a tool an agent will likely chain into update_zone or get_objects_in_zone.

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?

The tool takes no parameters, so there is no parameter semantics to explain; the baseline for a zero-parameter tool applies. The description instead spends its words on return-value semantics, which is the right allocation.

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?

States a specific verb and resource ('Get all zones in the garden') and immediately characterizes what a zone contains (editor geometry: centre + relative points). It also names the sibling it is not (get_site_analysis) for absolute polygons, so an agent can distinguish it without opening either schema.

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 get_site_analysis for absolute polygons and areas, implying this tool returns editor-relative geometry. It does not address the other close siblings (get_zone_types, get_zone_analysis, get_objects_in_zone), so the alternative-selection guidance is partial rather than exhaustive.

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