Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

set_geo_anchor

Places a garden plot at a real-world WGS84 coordinate by anchoring the editor origin, aligning north, sunlight, and OpenStreetMap. Use it for non-Polish plots after geocoding, then set the boundary.

Instructions

Set the garden's place: the real-world point (WGS84) at the editor origin. The plot becomes placed — north, sunlight and the OpenStreetMap background follow it — and the change is unsaved until save. Use it for a plot outside Poland (after geocode_address), then give the boundary with set_boundary; import_parcel sets both for a Polish parcel.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "set_geo_anchor"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesAnchor latitude (WGS84)
lonYesAnchor longitude (WGS84)
editorXNoEditor X coordinate (default 0)
editorYNoEditor Y coordinate (default 0)
dotsPerMeterNoScale factor (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: it discloses downstream effects (north, sunlight, OSM background follow the anchor) and persistence semantics ('the change is unsaved until save'). It stops short of stating whether an existing anchor is overwritten or what happens with invalid coordinates, so it is strong but not complete 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?

Two compact sentences, front-loaded with the action and followed by consequences and workflow. The parenthetical asides and em-dash clause are information-dense rather than padded, though the sentence is long enough that the usage guidance could be broken out more cleanly.

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?

Covers purpose, side effects, save-state, and the surrounding workflow (geocode_address → set_geo_anchor → set_boundary vs. import_parcel) for a georeferencing operation with five params. There is no output schema, so the description could say what is returned or what happens on an already-anchored plot, but nothing critical to correct invocation 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?

Schema coverage is 100%, so baseline is 3, but the description adds conceptual meaning by framing lat/lon as the real-world point at the editor origin — which clarifies how editorX/editorY relate to the geographic coordinates. It still does not explain dotsPerMeter's scaling effect beyond the schema's terse note.

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 ('Set the garden's place: the real-world point (WGS84) at the editor origin') and names the distinct counterpart, get_geo_anchor-style read versus this write. The scope is unambiguous and clearly separated from sibling georeferencing tools like set_boundary and import_parcel.

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?

Gives explicit when-to-use ('for a plot outside Poland'), a prerequisite ordering ('after geocode_address'), a follow-up step ('then give the boundary with set_boundary'), and an alternative that supersedes it for the Polish case ('import_parcel sets both'). An agent can route between the three tools without inference.

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