Skip to main content
Glama

Get Parcel

get_parcel

Look up a parcel in the official cadastre of 28 European countries (including the Basque Country and Navarre foral cadastres), by its official cadastral reference or by WGS84 coordinates, plus partial coverage in the United Kingdom (Scotland, coordinates only). Returns the reference, location, address, municipality, area, land use and the parcel outline when the official source provides them. The country is detected from the reference format or the point when omitted. Where the parcel has crop or land-use parts it also returns their count and a crop summary (crop and share of the area); the full list with outlines is get_parcel_subparcels. Croatia: cadastral municipality code + parcel number (334553-6250/3) or '6250/3 k.o. Zabok'. Ireland: registered land only. Every result names its official source and licence in the source field. Codes: ES Spain, PV Basque Country, NA Navarre, PT Portugal, FR France, IT Italy, DE Germany, AT Austria, CH Switzerland, LI Liechtenstein, BE Belgium, NL Netherlands, LU Luxembourg, PL Poland, CZ Czechia, SK Slovakia, SI Slovenia, HR Croatia, BG Bulgaria, GR Greece, CY Cyprus, DK Denmark, SE Sweden, NO Norway, FI Finland, IS Iceland, EE Estonia, LV Latvia, LT Lithuania, IE Ireland, UK United Kingdom.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of crop names (default English)
countryNoOptional country code. Omit to auto-detect. PV and NA are the Spanish foral cadastres.
latitudeNoLatitude in WGS84 (use with longitude instead of reference)
longitudeNoLongitude in WGS84 (use with latitude instead of reference)
referenceNoOfficial cadastral reference as written in the country (e.g. 9872023VH5797S0001WX, 750560000AB0001)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the returned fields, the coverage limits, that every result carries an official source and licence in the source field, and that country auto-detection happens server-side. It does not cover error behavior or failure modes for out-of-coverage parcels.

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?

Front-loaded with purpose and primary behavior, with country-specific caveats and then the code list at the end. The 30-entry code legend is long but earns some place because the schema enum gives codes without names; still, it is the bulkiest part of an otherwise tight definition.

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-only lookup with no output schema and full schema coverage, the description is complete: it explains what is returned, what happens when parameters are omitted, and where coverage stops. An agent could call this correctly without any other source.

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%, so the schema already documents all five parameters, making 3 the baseline. The description adds only marginal meaning beyond that: auto-detection logic for country and concrete reference formats for Croatia ('334553-6250/3', '6250/3 k.o. Zabok'), which are genuinely useful but narrow.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('look up a parcel in the official cadastre'), names the exact lookup keys (cadastral reference or WGS84 coordinates), and scopes coverage by country including the partial UK case. It also explicitly distinguishes itself from get_parcel_subparcels, which covers the full sub-parcel list.

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?

Gives clear context for use: reference OR coordinates, omit country to auto-detect, and route the full sub-parcel list to get_parcel_subparcels. It also flags real preconditions (Ireland registered land only, UK Scotland coordinates only). It stops short of naming exclusions relative to other siblings like resolve_reference or get_parcel_sigpac, so not a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.