chathome.lu — Luxembourg Real Estate

Get Affordability

get_affordability

Read-onlyIdempotent

Calculate Luxembourg mortgage affordability and state whether the property-price ceiling includes every acquisition cost or only currently known costs.

Input Schema

TableJSON Schema

Name	Required	Description
`marketRate`	No
`monthlyDebts`	No	Existing monthly debt payments
`residenceUse`	No	Residence use; omitted or unknown preserves an unconfirmed Bëllegen position
`householdType`	Yes
`loanTermYears`	No
`residencyType`	Yes
`employmentType`	Yes
`annualNetIncome`	Yes	User-confirmed annual household net income
`isFirstTimeBuyer`	No	Deprecated optional compatibility signal; never proves Bëllegen entitlement
`savingsAvailable`	Yes	Available savings/down payment
`isPersonalResidence`	No	Deprecated residence-use compatibility flag; prefer residenceUse
`maxDebtToIncomeRatio`	Yes	Explicit housing-payment share of net income, e.g. 0.35
`energyClassDiscountPct`	No
`bellegenAktEligibleBuyers`	No	Explicitly confirmed eligible acquirer count
`bellegenAktCreditAvailable`	No	Aggregate unused Bëllegen Akt balance explicitly confirmed for the acquirers
`floodZoneRateAdjustmentPct`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`trust`	Yes
`freshness`	Yes
`confidence`	Yes
`maxPropertyPrice`	Yes
`maxPropertyPriceCostBasis`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedAug 31, 2026

removedInput schema / properties / annualIncome

Removed value: -{
-  "description": "Gross annual household income",
-  "exclusiveMinimum": 0,
-  "type": "number"
-}

addedInput schema / properties / annualNetIncome

Added value: +{
+  "description": "User-confirmed annual household net income",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}

removedInput schema / properties / communeTaxRate

Removed value: -{
-  "exclusiveMinimum": 0,
-  "type": "number"
-}

addedInput schema / properties / maxDebtToIncomeRatio

Added value: +{
+  "description": "Explicit housing-payment share of net income, e.g. 0.35",
+  "exclusiveMinimum": 0,
+  "maximum": 0.6,
+  "type": "number"
+}

changedInput schema / required

Previous value: -[
-  "annualIncome",
-  "savingsAvailable",
-  "householdType",
-  "employmentType",
-  "residencyType"
-]New value: +[
+  "annualNetIncome",
+  "maxDebtToIncomeRatio",
+  "savingsAvailable",
+  "householdType",
+  "employmentType",
+  "residencyType"
+]

First observedAug 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds useful behavioral context by stating that the tool reports whether the property-price ceiling includes all acquisition costs or only currently known costs — a non-obvious caveat about how to interpret the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, front-loaded with the action, and no filler. The additional clause about acquisition-cost coverage is meaningful and earns its place.

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?

For a 16-param tool with an output schema and safety annotations, the description captures the core purpose and the most important interpretative caveat. It does not explain every parameter or selection context, but those gaps are partly filled by the input schema and sibling names.

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

Parameters2/5

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

Schema description coverage is only 56%, yet the description adds no parameter-level meaning. It does not explain key inputs such as annualNetIncome, maxDebtToIncomeRatio, savingsAvailable, or the residency/employment enums. The schema does partial work, but the description fails to compensate for the under-documented parameters.

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 uses a specific verb ('Calculate') with a specific resource ('Luxembourg mortgage affordability') and adds a distinctive output nuance about acquisition-cost coverage. This separates it clearly from siblings like get_price_estimate or get_market_context.

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

Usage Guidelines4/5

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

The description gives clear context for when to use the tool: anytime mortgage affordability in Luxembourg needs to be calculated. It does not explicitly name alternatives or exclusions, but the purpose is self-evidentifying against the sibling list.

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

All chathome.lu — Luxembourg Real Estate tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?