Assetfy

Get Parcel by Flurstücksnummer

assetfy_get_parcel_by_number

Read-onlyIdempotent

Look up ONE known parcel (Flurstück) by its cadastral designation — Gemarkung, optionally Flur, and Flurstücksnummer — as written in a Grundbuchauszug, Kaufvertrag, Exposé or Liegenschaftskataster extract ("Gemarkung Kressbronn, Flurstück 1924/1"). Returns the parcel with area in m² (Grundstücksgröße), coordinates, gml_id, Lagebezeichnung and assetfy_url; the gml_id then feeds every other parcel tool (overview, profile, buildings, planning law, land value, terrain, aerial image). Covers 15 of the 16 German states — only BAYERN is missing, because its cadastre is not openly licensed; there the parcel is found by address or coordinate instead. Leading zeros are irrelevant: Flur "3" finds "003". Many states (Baden-Württemberg among them) have no Flur, so leave it out when the source names none. Give the Gemarkung, not the Gemeinde: they often differ ("Gemeinde Kressbronn am Bodensee, Gemarkung Kressbronn"). An unknown Gemarkung comes back with did_you_mean; a name that exists in several states is searched in each of them, and bundesland or zip narrows it when the source names the state or postcode. This is a lookup of a designation, not a search: flurstuecksnummer is required.

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": {
      "gemarkung": "<gemarkung>",
      "flurstuecksnummer": "<flurstuecksnummer>"
    },
    "name": "assetfy_get_parcel_by_number"
  }
}

Input Schema

Name	Required	Description
`zip`	No	Postal code, optional. Narrows a Gemarkung name that exists more than once.
`flur`	No	Flur number, where the state has one. Leave out in Baden-Württemberg and wherever the source names none.
`gemarkung`	Yes	Cadastral district name (Gemarkung), case-insensitive, exact name. Not the Gemeinde.
`bundesland`	No	Bundesland key, e.g. baden_wuerttemberg, nrw. Optional — the Gemarkung index supplies it.
`include_geometry`	No	Add the parcel outline as GeoJSON in WGS84 (geometry).
`flurstuecksnummer`	Yes	Flurstücksnummer as Zähler/Nenner, e.g. 1924/1 or 458.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations (which already declare readOnly/idempotent/openWorld): discloses ambiguous-Gemarkung behavior (multi-state search, bundesland/zip narrowing), the did_you_mean response for unknown Gemarkungen, leading-zero normalization, and the Flur-less states. These are exactly the failure modes an agent needs to anticipate before calling.

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-loads the verb, resource and required designation before the caveats, and each sentence carries a distinct operational rule. It is on the long side with heavy parenthetical asides, but almost nothing is filler.

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?

There is no output schema, and the description compensates by enumerating the returned fields (area in m², coordinates, gml_id, Lagebezeichnung, assetfy_url) and by documenting coverage limits (15 of 16 states). For a 6-parameter lookup with two required inputs, nothing an agent needs is left implicit.

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; the description still earns credit by explaining the Gemarkung-vs-Gemeinde trap with a worked Kressbronn example and by clarifying that flur should be omitted where the state has none, plus the leading-zero irrelevance. It does not discuss include_geometry, though the schema covers that param adequately.

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 ONE known parcel (Flurstück)'), gives the exact input concept (Gemarkung + Flur + Flurstücksnummer) and explicitly frames it as a designation lookup rather than a search, which separates it from find_parcels and search_parcels_by_zip_and_area. The example designation makes the intended input form concrete.

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?

Names the source documents that supply the designation (Grundbuchauszug, Kaufvertrag, Exposé, Liegenschaftskataster), states the one case where this tool fails (BAYERN) and what to do instead (address or coordinate lookups), and explains that the returned gml_id feeds the downstream parcel tools. Alternative routing is explicit rather than inferred.

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

All Assetfy tools Inspect

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.