Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

get_geo_anchor

Retrieves the currently set geo-anchor for a garden design, confirming the real-world location tied to the plot before layout or review.

Instructions

Get the current geo-anchor (if set)

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_geo_anchor"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Get' implies a read, but it doesn't say what is returned when no anchor is set (null vs. error), what coordinate format the anchor uses, or whether the read has any side effects.

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 short phrase with no filler, front-loaded with the verb. It is efficient, though part of that efficiency comes from omitting information rather than from tight writing.

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

Completeness2/5

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

There is no output schema, so the description should explain what the anchor looks like when returned and what an unset anchor yields. For a simple getter this is a small but real gap, and the undefined domain term 'geo-anchor' compounds it.

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?

The tool takes zero parameters, so there is no parameter semantics to document; the baseline for a parameterless tool applies. Nothing in the description misleads about inputs.

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 ('Get') and resource ('geo-anchor'), so an agent knows this retrieves an anchor value. It does not define what a geo-anchor is or distinguish it from nearby siblings such as get_coordinate_system or get_full_state.

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?

The only usage signal is the parenthetical '(if set)', which hints the value may be absent but gives no guidance on when to call this versus get_coordinate_system, get_full_state, or set_geo_anchor. No prerequisites or follow-up steps are described.

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