Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

map_to_garden

Converts points on any survey map image or close-up into garden coordinates in metres, enabling plot corners to be used for boundary setup.

Instructions

Where points on the laid survey map are in the garden, in metres — e.g. the plot's corners read off the map, for set_boundary. Points are given on any view of the laid map's image (see zoom_image).

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": {
      "points": "<points>"
    },
    "name": "map_to_garden"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully states that output is in metres and that input points can come from any map view, but it omits return shape, ordering, and prerequisites such as whether the survey map must already be set.

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 description is two compact sentences with no filler and front-loads the conversion purpose. The phrasing 'Where points ... are in the garden' is slightly awkward, but the structure remains efficient.

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

Completeness3/5

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

For a one-parameter conversion tool with no output schema and no annotations, the description covers units and input views but leaves important gaps. It should state the return shape and prerequisites such as the survey map being laid before use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Top-level schema description coverage is 0%, though individual point fields have descriptions. The description adds that points are on any view of the laid survey map image and points to zoom_image, but it does not further explain the points array structure or coordinate conventions beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific transformation: converting points from the laid survey map image into garden coordinates in metres, with set_boundary as the downstream consumer. It lacks a crisp verb and title, but it is distinguishable from siblings like set_boundary and zoom_image.

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?

It gives a concrete use case — reading plot corners off the map for set_boundary — and says points may come from any view of the laid map image, referencing zoom_image. It does not state when not to use it or name alternative conversion paths, but the context is clear.

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