Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

get_parcel_by_address

Geocodes a Polish address and retrieves its parcel data for garden site planning; requests outside Poland are refused.

Instructions

Get parcel information by address (geocodes then looks up parcel). Poland only: refused for a garden placed outside Poland.

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": {
      "address": "<address>"
    },
    "name": "get_parcel_by_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesPolish address to find parcel for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose two non-obvious traits: an internal two-step geocode-then-lookup (extra latency/dependency) and a hard geographic restriction that causes refusal. It omits what happens when geocoding fails, what fields the parcel result contains, and whether any state is persisted.

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?

Two short sentences with the primary action front-loaded and the constraint second, which is the right ordering. The second sentence is awkwardly worded ("refused for a garden placed outside Poland"), a slight readability cost but not padding.

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 read-only lookup with one parameter and no output schema, the description covers the invocation but not the outcome — an agent cannot tell what parcel attributes come back or how large the response is. Since there is no output schema and no annotations, more of that burden should have been carried in text.

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% and the single address parameter is already documented as "Polish address to find parcel for", so the schema does the heavy lifting. The description adds only that the address is the input to the internal geocode step, with no format, completeness, or structure hints beyond that.

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 and resource ("Get parcel information") plus the lookup key ("by address") and the internal mechanism ("geocodes then looks up parcel"), which implicitly separates it from the get_parcel_by_coordinates and get_parcel_by_id siblings. It stops short of naming those alternatives explicitly, so the differentiation rests on the tool name.

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?

Supplies a real usage constraint ("Poland only") and a refusal condition for out-of-Poland cases, which tells the agent when the call will fail. It never says when to prefer this over geocode_address or get_parcel_by_coordinates, nor what to do after a refusal, so routing guidance is only implied by the name.

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