Skip to main content
Glama

Zornade - Italian Cadastre, Geospatial and Real Estate Data

Get cadastral parcel profile

zornade_parcel_by_id
Read-onlyIdempotent

Enriched cadastral parcel profile by FID or GML ID. Returns municipality, area, cadastral reference, and the requested data sections (risk, subsidence, terrain, buildings, economics, demographics, valuation, valuation_history, solar, POI, etc.). Geometry is omitted to keep the reply compact.

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": {
      "fid": "<fid>"
    },
    "name": "zornade_parcel_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
fidYesParcel FID number (example "28009975") or GML ID
includeNoComma-separated sections: risk,subsidence,terrain,population,buildings,economics,demographics,land_cover,land_use,valuation,valuation_history,coastal_erosion,cultural_heritage,poi,solar,nightlights,nightlights_v2. Default: risk,economics,solar,valuation. nightlights_v2 is the current VIIRS per-parcel section (measurement, not an estimate) and must be requested by name: it is not part of all. nightlights is deprecated (removal 2027-04-12).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / include / description
      Previous value: -"Comma-separated sections: risk,subsidence,terrain,population,buildings,economics,demographics,land_cover,land_use,valuation,valuation_history,coastal_erosion,cultural_heritage,poi,solar,nightlights. Default: risk,economics,solar,valuation"New value: +"Comma-separated sections: risk,subsidence,terrain,population,buildings,economics,demographics,land_cover,land_use,valuation,valuation_history,coastal_erosion,cultural_heritage,poi,solar,nightlights,nightlights_v2. Default: risk,economics,solar,valuation. nightlights_v2 is the current VIIRS per-parcel section (measurement, not an estimate) and must be requested by name: it is not part of all. nightlights is deprecated (removal 2027-04-12)."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and open-world behavior, so the safety profile is covered. The description still adds real value beyond that by disclosing that geometry is deliberately omitted to keep responses compact — a non-obvious output constraint an agent would otherwise discover only after calling. It stops short of mentioning rate limits, error behavior, or whether geometry can be obtained at all.

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?

Three short sentences, front-loaded with the identity of the tool and followed by returns and the geometry caveat; nothing is padding. The only blemish is the trailing 'etc.' in the section list, which is vaguer than the exhaustive schema and slightly undercuts an otherwise tight statement.

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?

With no output schema, the description carries the burden of describing returns, and it does name the headline fields and the section-based response shape. The geometry omission is the key behavioral fact an agent needs. Missing only edge-case behavior (invalid FID, empty sections, whether geometry is ever retrievable).

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%, so the schema already documents both parameters, including the section list and the nightlights deprecation. The description reinforces the selective-section model ('the requested data sections') but adds no syntax, format, or default behavior beyond what the schema states, and its abbreviated 'etc.' list is actually less precise than the schema's enumeration.

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?

The description opens with a specific verb-plus-resource statement ('Enriched cadastral parcel profile by FID or GML ID') and enumerates what comes back (municipality, area, cadastral reference, selected sections). It is clearly a single-record lookup, which distinguishes it in spirit from the sibling search/locate tools, but it never names an alternative, so an agent must infer the boundary itself.

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?

Usage is only implied: the tool takes an identifier, so an agent understands it is for retrieving a known parcel rather than discovering one. There is no explicit 'use zornade_parcel_search first if you only have an address' routing, and no statement of when-not to call it or what happens with an unknown ID.

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.