Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

set_garden_rotation

Set the garden's north orientation in degrees to align the design with true compass directions and ensure accurate plant placement and sun exposure.

Instructions

Set the garden's north orientation in degrees

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": {
      "degrees": "<degrees>"
    },
    "name": "set_garden_rotation"
  }
}

Input Schema

NameRequiredDescriptionDefault
degreesYesRotation in degrees (0 = north up, 90 = east up)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a mutation but says nothing about persistence (e.g., whether a separate save is required, given the sibling save/undo/redo tools), what happens to already-placed objects, or what is returned. Only the unit's meaning is clarified.

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?

A single front-loaded sentence with no filler, so every word earns its place. It is arguably too terse rather than padded, which is a completeness issue rather than a conciseness one.

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 setter with no output schema and no annotations, the description is minimally sufficient to pick the tool and supply a value. It leaves open whether the rotation takes effect immediately or is staged for save, which matters given the presence of save/undo siblings.

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?

Schema description coverage is 100% and the parameter description already explains the 0/90 convention, so the schema does the heavy lifting. The description's mention of "north orientation in degrees" adds nothing beyond what the schema states; baseline 3 is correct.

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?

States a specific verb ("Set") and resource ("garden's north orientation") with the unit of measure, so the agent knows exactly what changes. It does not explicitly distinguish itself from orientation-adjacent siblings like set_geo_anchor, set_boundary, or get_coordinate_system, which keeps it from a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives such as set_geo_anchor or get_coordinate_system for related orientation concerns. The agent must infer usage purely from the name and the single sentence.

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