Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

add_pins

Add multiple garden context pins in one call to mark doors, windows, gates, and views; returns pin IDs for efficient layout editing.

Instructions

Add multiple context pins in a single call. Returns array of pin IDs. Use this instead of calling add_pin multiple times.

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": {
      "pins": "<pins>"
    },
    "name": "add_pins"
  }
}

Input Schema

NameRequiredDescriptionDefault
pinsYesArray of pin specifications

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the batch behavior and the return shape (array of pin IDs) and explains what each pin type visually represents, but it says nothing about required setup state, failure behavior for invalid types or out-of-bounds coordinates, or whether the batch is atomic.

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?

Purpose, return value, and sibling routing are front-loaded in three short sentences, followed by a scannable bulleted type glossary. No sentence is redundant, and the list format makes the enum semantics fast to parse.

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 single-parameter batch tool with a fully documented nested schema, the description covers purpose, batching rationale, return value, and type semantics. The remaining gap is the implied dependency on set_units and the coordinate system, which is referenced only inside the schema property text rather than the description.

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 description coverage is 100%, so the baseline is 3, and the description earns an increment by giving real-world meaning to each enum value (door = main entrance in red, view_bad = undesirable view to screen, etc.) that the bare enum does not convey. The x/y/label/notes fields add no extra meaning, but they are already fully documented in the 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 ('Add multiple context pins'), the batch scope ('in a single call'), and the return value ('array of pin IDs'). It explicitly names the sibling add_pin, so an agent can distinguish batch from single-pin creation without opening either schema.

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 selection rule: 'Use this instead of calling add_pin multiple times,' which routes multi-pin cases here and single-pin cases to the sibling. It stops short of stating prerequisites, such as needing a coordinate system or units set before placement, so it is clear context without full exclusions.

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