Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

get_full_state

Retrieve the full garden state at session start, or return only the summary and coordinate system to avoid token limits on large scenes.

Instructions

Get the garden state. Default: full payload (summary + zones + pins + objects + layer visibility + view mode + geo-anchor + coordinate system) — use at session start. Pass summary_only=true on large scenes to skip the heavy arrays and return just the summary block + coordinateSystem (avoids exceeding the tool-result token budget).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_full_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
summary_onlyNoWhen true, return only { summary, coordinateSystem }. Skips zones/pins/objects/gardenInfo/layerVisibility/viewMode/geoAnchor arrays. Recommended for scenes with many objects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A4.1/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 usefully discloses that the default response is heavy and may exceed the tool-result token budget. It also explains that summary_only skips the heavy arrays, though it does not explicitly state read-only safety, side effects, or permissions.

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?

The description is front-loaded and compact: it states the default behavior first, then the summary_only escape hatch and its purpose. Every sentence adds useful operational context without waste.

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

Completeness5/5

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

For a read-style state retrieval tool with no output schema, the description explains both the default return structure and the reduced return structure under summary_only. That is sufficient for an agent to call it correctly and understand the response shape.

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 coverage is 100%, so the parameter is already fully documented. The description restates the summary_only behavior and adds the token-budget rationale, but it does not add much beyond what the schema already provides.

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 clearly states a specific verb and resource: 'Get the garden state.' It also enumerates the default payload, making the tool's scope concrete, but it does not explicitly distinguish this tool from sibling getters like get_zones, get_pins, or get_objects.

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 clear usage context: 'use at session start' for the full payload, and pass summary_only=true on large scenes. This covers the main when-to-use condition and the alternative mode, but it does not mention when to prefer individual sibling getters instead.

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