Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CATASTROGPS_API_KEYYesYour API key
CATASTROGPS_API_URLNoAPI base URLhttps://api.parcelgps.com
CATASTROGPS_TIMEOUTNoRequest timeout in ms. Official cadastres can be slow20000

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_parcelA

Look up a cadastral parcel in 29 European countries plus the Basque Country and Navarre (31 codes) by its official cadastral reference or by WGS84 coordinates. 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. United Kingdom: coordinates only. 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.

search_addressA

Find the Spanish cadastral reference for a postal address typed as free text, e.g. 'Calle Mallorca 213, Barcelona' or 'Avenida de la Constitución 1, 41004 Sevilla'. Works for Spain under the central Catastro (not the Basque Country or Navarre, and not other countries: use get_parcel with coordinates there). Include the street number and the municipality or postal code. Then call get_parcel with the returned reference and country ES.

get_boundariesA

Get the outline of a cadastral parcel as GeoJSON and/or a [lat, lng] ring, plus its centroid and area, for mapping and GIS work. Accepts references from the same 30 codes as get_parcel (every covered country except the United Kingdom, which is coordinates only).

get_solar_potentialA

Estimate the photovoltaic potential of a parcel from PVGIS (European Commission JRC): installable kWp, yearly production, savings, payback, CO2 avoided, optimal tilt and orientation. Available for Spain (ES, PV, NA), Portugal, France, Italy and Germany.

get_agricultureA

Agricultural context for a rural parcel: land use and main crop from the agricultural parcel registry (SIGPAC in Spain, with slope, altitude and irrigation), vegetation index (NDVI) and a reference crop price when available. Richest in Spain; also Portugal, France, Italy and Germany. Field names are returned in Spanish, as the API sends them.

get_market_dataA

Aggregated land and property price reference for the area around a parcel. Never returns individual sales. Price figures exist only in France (DVF recorded sales: average EUR/m2, number of sales, last sale date, estimated value), Italy (OMI zone values from Agenzia delle Entrate) and Germany (official Bodenrichtwert land value per m2, North Rhine-Westphalia only; elsewhere in Germany it answers available=false). For Spain (ES, PV, NA) and Portugal it returns a reference note without figures: there is no per-parcel price source yet. One API call.

get_investment_scoreA

Investment score (0-100) for a parcel with a rating (excelente, bueno, moderado, bajo, muy_bajo) and qualitative factor levels (high/medium/low/not_available), never the formula. Built from the data the API can gather for that country: solar potential (PVGIS) and agricultural use in ES, PV, NA, PT, FR, IT and DE; the market factor only in France, Italy and Germany (North Rhine-Westphalia). Accessibility and risk are not computed yet and come back as not_available, so the score is relative to the factors that were available. Other countries are not supported. One API call.

get_value_historyA

Snapshots of a parcel as the official cadastre reported it over time: area and land use, at most one snapshot every 30 days. History starts the first time anyone looks the parcel up through CatastroGPS (get_parcel) and grows from there, so a parcel never queried before returns an empty list. The official cadastral value is not recorded yet (always null). change_pct is the area change between the oldest and newest snapshot. Recorded for ES, PV, NA, PT, FR, IT, DE and AT. One API call.

compare_parcelsA

Compare 2 or 3 parcels side by side: location, solar potential, agricultural use and investment score (0-100 with rating). Parcels can be in different countries: ES (Spain, common regime), PT, FR, IT and DE. The Basque Country and Navarre are not supported here (use the single-parcel tools). Area, land use and municipality are only filled for Spain. No market prices. A parcel that is not found comes back with an error and the others are still compared. One API call for the whole comparison.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 9 tools

Disambiguation4/5

Each tool targets a distinct data type or action: lookup (get_parcel), address resolution (search_address), geometry (get_boundaries), and single-domain analytics (solar, agriculture, market, investment, history) plus comparison. The only mild overlap is get_parcel returning an outline while get_boundaries also returns outline/centroid, but the descriptions clearly delineate them.

Naming Consistency5/5

All nine tools follow a consistent verb_noun pattern (get_parcel, get_boundaries, get_solar_potential, compare_parcels, search_address). The verb varies (get/search/compare) only because the actions genuinely differ, and the spelling/casing style is uniform.

Tool Count5/5

Nine tools is well within a healthy range and each maps to a clearly earned capability for a cadastral-data service. Nothing appears redundant or padded.

Completeness4/5

The surface covers lookup, address search, geometry, and the major analytical dimensions (solar, agriculture, market, investment, temporal history) plus comparison, forming a coherent lifecycle. Minor gaps exist, such as no export/batch or explicit coverage-listing operation, but core workflows are fully supported.