Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

import_buildings

Scan the current imported parcel and its 10 m margin via ULDK to add discovered building footprints as building zones; import the parcel first.

Instructions

Scan the imported parcel + 10 m margin via ULDK and add discovered building footprints as building zones. Requires import_parcel first — uses the current parcel and geo-anchor. Blocks until the scan completes; typically 1–2 minutes for a residential parcel because ULDK is slow, so do not retry on perceived stalls. Re-runs are safe: buildings already imported are deduped by parcelBuildingId and reported under skipped. Returns { success, count, added, skipped, buildings: [{ zoneId, parcelBuildingId, functionLabel, centerX, centerY, width, height }] } (meters). The largest building whose center sits inside the parcel is usually the user's house; the rest are neighbors. Poland only: refused for a garden placed outside Poland.

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": "import_buildings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A4.9/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 burden and does so well: it discloses blocking behavior and expected duration (1–2 minutes), idempotency semantics via parcelBuildingId dedup with a 'skipped' count, the refusal condition, and the exact response shape. Rate-limit/auth details are the only minor omission.

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?

The core action is front-loaded in the first sentence, followed by prerequisite, timing warning, idempotency, and return shape in a logical order. The inline return schema is dense but every clause conveys actionable information; nothing is filler.

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?

Despite having no output schema, the description fully describes the return payload, including field names and units (meters), and explains how to interpret results ('largest building whose center sits inside the parcel is usually the user's house'). Nothing an agent needs to call this correctly is missing.

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 zero parameters, so the baseline is 4. The description correctly implies the implicit inputs (current parcel and geo-anchor set by import_parcel) rather than leaving them unexplained, which is the only meaningful semantic content for a parameterless tool.

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: 'Scan the imported parcel + 10 m margin via ULDK and add discovered building footprints as building zones.' It is clearly distinguishable from sibling tools like import_parcel (prerequisite) and add_zone (manual creation) because it explains the scan-and-import mechanism.

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

Usage Guidelines5/5

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

Explicitly names the prerequisite ('Requires import_parcel first'), the geographic exclusion ('Poland only: refused for a garden placed outside Poland'), the re-run policy ('Re-runs are safe ... deduped'), and an operational warning ('do not retry on perceived stalls'). Both when-to-use and when-not-to-use are covered.

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