Skip to main content
Glama
Sign In

Cenogram - Polish Real Estate Data

by pl.cenogram.mcp
OverviewDiscussionsAdmin

resolve_parcel

Read-only

Resolve a land parcel to its cadastral identity using exactly ONE of:

  • parcelId: a full cadastral id ('142907_2.0014.342/5' or the '-' form) or internal UUID.

  • q: a full id, a UUID, or 'locality name + parcel number' (e.g. 'Sabnie 342/5'): the name is a gmina or cadastral precinct (obręb), matched exactly, case-insensitively; a gmina name plus a number also works for a gmina made of several precincts (e.g. 'Ełk 461/3'). An ambiguous name returns candidates, not a guess. NOT a street address: for that use list_parcels_in_area(street=, buildingNumber=).

  • lat & lng: a WGS84 point inside the parcel (a road parcel is flagged: the point probably fell on the street).

  • prefix: a cadastral id PREFIX (min 3 chars, e.g. '146518_8.01'), autocomplete only; limit (1-10, default 10) goes with it. Never by area: for parcels in a place or shape use list_parcels_in_area. Returns matching parcels with district, area and coordinates; 'truncated' when capped. not_covered: for a FULL id, we could not confirm the parcel live; in the DISCOVERY modes (name + number, coordinate) only "not among the parcels we hold" (near-complete, not live) - a fresh change or odd spelling is likelier than a missing parcel, so never report "no such parcel". not_computed = lookup did not finish, also not a finding. corpus_coverage says how much of the register was searched. Then feed the id to search_transactions(parcelId) for its sale history. Free.

Input Schema

NameRequiredDescriptionDefault
qNoFull cadastral id, UUID, or 'locality name + parcel number' (e.g. 'Sabnie 342/5'); not a street address.
latNoLatitude WGS84; pair with lng.
lngNoLongitude WGS84; pair with lat.
limitNoMax results (1-10, default 10); only with prefix.
prefixNoCadastral id prefix (min 3 chars), e.g. '146518_8.01'; not combined with the other modes.
parcelIdNoFull cadastral id (slash or dash form) or internal UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max results (1-10, default 10); only with prefix.",
+  "maximum": 10,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / prefix
      Added value: +{
+  "description": "Cadastral id prefix (min 3 chars), e.g. '146518_8.01'; not combined with the other modes.",
+  "maxLength": 200,
+  "minLength": 3,
+  "type": "string"
+}
  2. Changed4 schema fields changed
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude WGS84; pair with lng. Exclusive with q and parcelId."New value: +"Latitude WGS84; pair with lng."
    • changedInput schema / properties / lng / description
      Previous value: -"Longitude WGS84; pair with lat. Exclusive with q and parcelId."New value: +"Longitude WGS84; pair with lat."
    • changedInput schema / properties / parcelId / description
      Previous value: -"Full cadastral id (slash or dash form) or internal UUID. Exclusive with q and lat/lng."New value: +"Full cadastral id (slash or dash form) or internal UUID."
    • changedInput schema / properties / q / description
      Previous value: -"Full cadastral id, UUID, or 'locality name + parcel number' (e.g. 'Sabnie 342/5'); not a street address. Exclusive with parcelId and lat/lng."New value: +"Full cadastral id, UUID, or 'locality name + parcel number' (e.g. 'Sabnie 342/5'); not a street address."
  3. Changed4 schema fields changed
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude WGS84. Must be paired with lng. Mutually exclusive with q and parcelId."New value: +"Latitude WGS84; pair with lng. Exclusive with q and parcelId."
    • changedInput schema / properties / lng / description
      Previous value: -"Longitude WGS84. Must be paired with lat. Mutually exclusive with q and parcelId."New value: +"Longitude WGS84; pair with lat. Exclusive with q and parcelId."
    • changedInput schema / properties / parcelId / description
      Previous value: -"Full cadastral id (slash or dash form) or internal UUID. Mutually exclusive with q and lat/lng."New value: +"Full cadastral id (slash or dash form) or internal UUID. Exclusive with q and lat/lng."
    • changedInput schema / properties / q / description
      Previous value: -"Full cadastral id, a UUID, or 'locality name + parcel number' (e.g. 'Sabnie 342/5') — the name may be a gmina or a cadastral precinct (obręb). NOT a street address: for a street + building number use list_parcels_in_area instead. Mutually exclusive with parcelId and lat/lng."New value: +"Full cadastral id, UUID, or 'locality name + parcel number' (e.g. 'Sabnie 342/5'); not a street address. Exclusive with parcelId and lat/lng."
  4. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Full cadastral id, a UUID, or 'locality name + parcel number' (e.g. 'Sabnie 342/5') — the name may be a gmina or a cadastral precinct (obręb). Mutually exclusive with parcelId and lat/lng."New value: +"Full cadastral id, a UUID, or 'locality name + parcel number' (e.g. 'Sabnie 342/5') — the name may be a gmina or a cadastral precinct (obręb). NOT a street address: for a street + building number use list_parcels_in_area instead. Mutually exclusive with parcelId and lat/lng."
  5. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Full cadastral id, a UUID, or 'locality name + parcel number' (e.g. 'Sabnie 342/5'). Mutually exclusive with parcelId and lat/lng."New value: +"Full cadastral id, a UUID, or 'locality name + parcel number' (e.g. 'Sabnie 342/5') — the name may be a gmina or a cadastral precinct (obręb). Mutually exclusive with parcelId and lat/lng."
  6. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the read-only/open-world safety profile; the description adds substantive behavior beyond them: ambiguity yields candidates instead of a guess, road parcels are flagged, 'truncated' marks capped results, and the critical caveat that not_covered/not_computed are not evidence of a missing parcel. It also states ambiguity handling and cost ('Free'). This is exactly the kind of context annotations cannot carry.

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?

The mode list is front-loaded and scannable, and the alternatives are placed inline where they matter. It loses a point for density: the not_covered/not_computed paragraph packs several nested caveats into one long run-on, and a few details (limit default, supported id forms) duplicate the schema.

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?

With no output schema, the description still explains what comes back (parcels with district, area, coordinates), introduces the 'truncated' flag and the not_covered/not_computed/corpus_coverage status semantics. For a six-parameter, multi-mode lookup tool this leaves nothing an agent needs missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further: exact case-insensitive name matching, gmina vs cadastral precinct (obręb) acceptance, multi-precinct gmina names, WGS84 point-in-parcel semantics, prefix as autocomplete-only with min 3 chars. The remaining gap is that the mutual exclusivity rules are stated per-bullet rather than as one crisp guard, and limit's default is repeated from the schema.

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?

The description opens with a specific verb and resource ('Resolve a land parcel to its cadastral identity') and then enumerates the four mutually exclusive input modes. It explicitly distinguishes itself from siblings list_parcels_in_area and search_transactions, so an agent can route without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Every mode carries a 'use this when' clause, and two negative cases are named with the correct alternative ('NOT a street address: for that use list_parcels_in_area'; 'Never by area: for parcels in a place or shape use list_parcels_in_area'). The trailing instruction to chain into search_transactions(parcelId) gives an explicit next step.

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

All Cenogram - Polish Real Estate Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources