Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

add_pin

Place context pins for doors, windows, gates, and views on a garden plan using x/y coordinates; returns the pin ID for layout reference.

Instructions

Add a context pin to the garden. Returns the pin ID.

Available pin types: • door — main entrance door (red) • patio_door — patio/garden door (teal) • window — window opening (blue) • gate — garden gate/entrance (green) • view_good — desirable view direction (yellow) • view_bad — undesirable view to screen (grey)

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": {
      "pinType": "<pinType>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "add_pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX position — units determined by set_units (default 'm', meters)
yYesY position — units determined by set_units (default 'm', meters)
labelNoOptional: Custom label for the pin
notesNoOptional: Design notes — context about this pin, what it means for the layout
pinTypeYesType of pin to create

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 at all, the description carries the full burden and does contribute the return value (pin ID) and semantic meaning for each pin type. It is silent on mutation side effects an agent would care about: whether the garden must already exist, whether the coordinate system must be set first, undo behavior, and boundary/validation rules.

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?

Front-loaded with the action and return value in a single sentence, then a scannable bulleted type list. The color annotations (red, teal, blue) are visual trivia that do not help tool selection, but they are brief and do not obscure the core information.

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?

For a 5-parameter creation tool with no output schema, the description covers the action, the return value, and the full type vocabulary, and the schema handles coordinate units. Remaining gaps are preconditions (units set, garden exists) and how the new pin interacts with zones or layers.

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 the baseline is 3; the description earns an extra point by explaining what each enum value of pinType actually denotes, which the schema only lists as bare strings. It adds nothing for x/y/label/notes, but those are already well documented in the schema.

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?

"Add a context pin to the garden" names a specific verb and resource, and "Returns the pin ID" states the outcome. It does not differentiate itself from the closely named siblings add_pins (bulk), get_pins, or delete_pin, so an agent must infer the singular-vs-batch split.

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

Usage Guidelines3/5

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

The pin-type list implicitly guides selection by explaining what each type represents ("desirable view direction", "undesirable view to screen"), which is genuinely useful for choosing a type. However, there is no explicit when-to-use guidance, no mention of when to prefer add_pins for multiple pins, and no note on when to supply label/notes.

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