Skip to main content
Glama
Sign In

chathome.lu — Luxembourg Real Estate

by lu.chathome
OverviewDiscussionsAdmin

Get Mortgage Rates

get_mortgage_rates
Read-onlyIdempotent

Get current source-dated full-term fixed mortgage market observations supported by ChatHome's rates feed. Returns availability and observation date; stale, undated or official initial-fixation bands never become current full-term quotes. These are not personal bank offers. If unavailable, ask for an explicit rate assumption before calculate_mortgage.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sourceUrlYes
dataStatusYes
limitationYes
availabilityYes
bankExamplesYes
officialRatesYes
schemaVersionYes
startingRatesYes
referenceEditionYes
bankReferenceEditionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedOutput schema / properties / bankExamples
      Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / bankReferenceEdition
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • removedOutput schema / properties / fullTermFixedRates
      Removed value: -{
-  "additionalProperties": {
-    "type": "number"
-  },
-  "propertyNames": {
-    "type": "string"
-  },
-  "type": "object"
-}
    • removedOutput schema / properties / observedAt
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • addedOutput schema / properties / officialRates
      Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / referenceEdition
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedOutput schema / properties / startingRates
      Added value: +{
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "schemaVersion",
-  "availability",
-  "fullTermFixedRates",
-  "observedAt",
-  "dataStatus",
-  "sourceUrl",
-  "limitation"
-]New value: +[
+  "schemaVersion",
+  "availability",
+  "bankExamples",
+  "officialRates",
+  "startingRates",
+  "referenceEdition",
+  "bankReferenceEdition",
+  "dataStatus",
+  "sourceUrl",
+  "limitation"
+]
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important data-quality behavior: stale, undated, or official initial-fixation bands are excluded from current full-term quotes. It also clarifies that these are market observations rather than personal offers and states what is returned regarding availability and observation date.

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?

The description is front-loaded with the core purpose and then adds only high-value caveats, return context, and a fallback instruction. Every sentence contributes useful guidance without repetition.

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?

Given zero parameters, rich annotations, and an output schema, the description supplies the necessary context: what the rates represent, what is excluded, what is returned, and how to proceed if unavailable. Nothing essential for correct invocation appears to be 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?

This tool has zero parameters, so the baseline score is 4. There is no parameter meaning for the description to add beyond 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 names a specific verb and resource: getting current source-dated full-term fixed mortgage market observations. It also distinguishes the data from personal bank offers and from the downstream calculate_mortgage action, so an agent can understand its role without ambiguity.

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?

It provides a clear fallback path: if rates are unavailable, ask for an explicit rate assumption before calling calculate_mortgage. This explicitly names the relevant sibling tool and the condition for using it. It does not spell out every possible alternative, but the primary workflow is clear.

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 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