Skip to main content
Glama
Sign In
Garden Design MCP Server

Garden Design MCP Server

by zaprojektuj-ogrod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_site_analysis

Computes parcel area, facade endpoints, and garden depth from imported site data so you can place door pins on the correct facade and check if a terrace or bed fits before drawing zones.

Instructions

Measured site facts for placing pins and zones, computed from the parcel boundary and building zones (call after import_parcel + import_buildings). Returns (metres, garden coordinates): the parcel area and its edges by compass side; the user's house (largest building centred in the parcel) with each facade's compass side, length, from/to endpoints, midpoint, outward normal, whether it is a shared (party) wall, and gardenDepth — the free distance from the facade straight out to the boundary; neighbouring buildings with direction and whether attached; total garden area. Use it to put door pins ON the right facade and to check whether a terrace or bed fits on a side before drawing zones.

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_site_analysis"
  }
}

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?

With no annotations, the description carries the full burden, and it does so by disclosing that results are derived from the boundaries (not raw input echo), naming the units, and defining derived concepts like 'gardenDepth' and 'largest building centred in the parcel'. It does not state behavior on missing/partial parcel data or whether results are cached, but it implies failure without the prerequisite imports.

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?

The purpose and prerequisite are front-loaded, and the return-field enumeration, though long, is dense with decision-relevant detail rather than filler. The single paragraph is harder to scan than a short bullet list would be, which keeps it below a 5.

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?

There is no output schema and no parameters, so the description must supply the return contract, and it does: parcel area and edges, house facades with side/length/endpoints/midpoint/normal/party-wall flag/gardenDepth, neighbouring buildings, and total garden area. An agent can decide whether to call it and how to use the result without opening anything else.

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 there is nothing to disambiguate; the description instead spends its space explaining the outputs. That is the right allocation given the empty 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?

States a specific verb and resource ('Measured site facts ... computed from the parcel boundary and building zones') with explicit output scope in metres/garden coordinates. It clearly distinguishes itself from siblings like get_garden_info and get_zone_analysis by being the pre-drawing measurement source.

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 prerequisite ('call after import_parcel + import_buildings') and two concrete use cases (placing door pins on a facade, checking whether a terrace or bed fits before drawing zones). It stops short of naming alternative tools or saying when not to call it.

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

Deploy Server

Other Tools