Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

get_parcel_by_id

Retrieve parcel information by parcel ID to support garden design in Poland; requests for parcels outside Poland are refused.

Instructions

Get parcel information by parcel ID. 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": {
      "parcelId": "<parcelId>"
    },
    "name": "get_parcel_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
parcelIdYesParcel ID, e.g., '146510_8.0310.60'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose one real behavioral trait beyond the schema — the tool refuses requests for gardens outside Poland — which is valuable, but it says nothing about the read-only nature, permissions, error shape, or what 'parcel information' includes.

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 first and the geographic constraint second; nothing is wasted. The phrasing "refused for a garden placed outside Poland" is slightly awkward but does not obscure meaning.

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 read lookup with full schema coverage, the definition covers the essential call path and its main constraint. The remaining gap — what fields the returned parcel object contains — is mitigated by the simplicity of the tool, though with no output schema an agent still lacks shape information.

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?

Only one parameter and 100% schema coverage: the schema already defines parcelId and even gives a format example. The description adds no format, validation, or prefix/suffix detail beyond what the schema provides, so the baseline 3 applies.

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") and the retrieval key ("by parcel ID"), which implicitly distinguishes it from the sibling lookups get_parcel_by_coordinates and get_parcel_by_address. It does not, however, explicitly contrast itself with those siblings or with import_parcel, so an agent must infer the routing.

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?

The Poland-only restriction gives a clear failure condition, which is genuine usage context. But there is no explicit guidance on when to prefer this over get_parcel_by_coordinates / get_parcel_by_address, nor any note about prerequisites or what to do when the parcel is outside Poland.

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