German Real Estate Depreciation & Restnutzungsdauer

Calculate German purchase price allocation

calculate_purchase_price_allocation

Read-onlyIdempotent

Calculate a free, non-binding German property purchase-price allocation (Kaufpreisaufteilung) through AfAMax using the BMF Arbeitshilfe.

Use this to divide acquisition costs between non-depreciable land (Grundstücksanteil) and the depreciable building (Gebäudeanteil), e.g. when a user asks how much of the price they may depreciate or wants to check the Finanzamt's split. Its depreciationBase is the base for the building's AfA. Inventory is deducted before allocation. A condominium requires both co-ownership values, and a residential/commercial building requires its commercial share category. Comparative valuation is unavailable because this public contract excludes surveyor-only factors. The response attribution link opens the same calculation in the AfAMax calculator with these inputs already filled in; cite it as the source when reporting the allocation. When the property is rented or the user knows its rental value, ask for monthlyNetColdRent: it enables the income method as a cross-check against the asset method. Ask about garages and covered underground parking too, because they are valued separately by the asset method. Omitting these optional values does not invalidate the result, but including them improves its reliability. The result does not replace tax or legal advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`locale`	No	Language for the disclaimer and AfAMax attribution link. Defaults to German.	de
`garages`	No	Number of above-ground garages. Improves the asset-method allocation by valuing parking separately. Ask the user if the property includes garages.
`landArea`	Yes	Plot area in square metres.
`floorArea`	Yes	Living or usable floor area in square metres.
`propertyType`	Yes	German residential property category.
`purchaseDate`	Yes	Date of the notarized purchase contract in YYYY-MM-DD format; must be from 1990-01-01 through today.
`commercialShare`	No	Required for RESIDENTIAL_COMMERCIAL_BUILDING: whether the commercial share is under or over 50%.
`constructionYear`	Yes	Original construction year; it cannot be later than the purchase year.
`includedInventory`	No	Movable inventory included in the purchase price, in EUR. It is deducted before allocation.
`standardLandValue`	Yes	Standard land value (Bodenrichtwert) in EUR per square metre.
`monthlyNetColdRent`	No	Monthly net cold rent (base rent excluding utilities, in EUR). Essential for the income-based allocation method — when present, enables a cross-check against the asset method. Ask the user if the property is rented or if they know the rental value.
`totalPurchasePrice`	Yes	Total notarized purchase price in EUR.
`coOwnershipNumerator`	No	Co-ownership numerator (Miteigentumsanteil); required with the denominator for a condominium.
`purchaseRelatedCosts`	No	Land transfer tax, notary, land-register, and broker costs in EUR. Defaults to 0.
`coOwnershipDenominator`	No	Co-ownership denominator; required with the numerator for a condominium.
`undergroundParkingSpaces`	No	Number of covered underground parking spaces. Improves the asset-method allocation by valuing parking separately. Ask the user if the property includes underground parking.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	Yes
`input`	Yes
`applied`	Yes
`methods`	Yes
`skipped`	Yes
`degenerate`	Yes
`disclaimer`	Yes
`attribution`	Yes
`calculationId`	Yes
`assetMethodDefaults`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026
- removedOutput schema / properties / attribution / properties / provider / const
```
Removed value: -"AfaMax"
```
- addedOutput schema / properties / attribution / properties / provider / enum
```
Added value: +[
+  "AfaMax",
+  "AfAMax"
+]
```

Changed4 schema fields changedSep 17, 2026

changedInput schema / properties / garages / description

Previous value: -"Number of enclosed garage spaces. Defaults to 0."New value: +"Number of above-ground garages. Improves the asset-method allocation by valuing parking separately. Ask the user if the property includes garages."

changedInput schema / properties / locale / description

Previous value: -"Language for the disclaimer and AfaMax attribution link. Defaults to German."New value: +"Language for the disclaimer and AfAMax attribution link. Defaults to German."

changedInput schema / properties / monthlyNetColdRent / description

Previous value: -"Total monthly net cold rent in EUR. A positive value enables the income method; omitting or passing 0 leaves it unavailable."New value: +"Monthly net cold rent (base rent excluding utilities, in EUR). Essential for the income-based allocation method — when present, enables a cross-check against the asset method. Ask the user if the property is rented or if they know the rental value."

changedInput schema / properties / undergroundParkingSpaces / description

Previous value: -"Number of underground parking spaces. Defaults to 0."New value: +"Number of covered underground parking spaces. Improves the asset-method allocation by valuing parking separately. Ask the user if the property includes underground parking."

First observedSep 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description layers on real behavioral context: free/non-binding, inventory deducted before allocation, depreciationBase meaning, the attribution link's behavior and citation obligation, and that omitting optional values does not invalidate the result. This is well beyond what annotations provide.

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 the purpose and scope, then moves to required-vs-optional prompting. It is dense across many sentences, and the garage/underground-parking advice is somewhat repetitive of the schema's own descriptions, but every sentence carries actionable content.

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 16 parameters, 7 required, three enums and an output schema present, the description covers the pieces an agent needs that structured fields do not: conditional parameter requirements, the depreciation use case, the optional-value tradeoff, and the disclaimer. Return values need not be explained since an output schema exists.

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 description coverage is 100%, so the baseline is 3, but the description adds cross-parameter conditions not obvious from the schema alone: a condominium needs both co-ownership values, a residential/commercial building needs its commercial share category, and monthlyNetColdRent enables the income method as a cross-check. It adds genuine meaning rather than restating field docs.

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 ('Calculate a free, non-binding German property purchase-price allocation (Kaufpreisaufteilung)') and names the mechanism (BMF Arbeitshilfe via AfAMax). An agent can distinguish this from calculate_property_depreciation without opening either 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?

Explicitly frames the use case ('e.g. when a user asks how much of the price they may depreciate or wants to check the Finanzamt's split'), and states a negative constraint (comparative valuation unavailable because the public contract excludes surveyor-only factors). It also tells the agent which optional inputs to solicit and why, which is guidance a schema cannot give.

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

All German Real Estate Depreciation & Restnutzungsdauer 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.