chathome.lu — Luxembourg Real Estate

Compare Listings

compare_listings

Read-onlyIdempotent

Compare two to eight listings through one normalized AgentListing v2 response, including known and estimated costs, availability, property facts, official flood/noise checks, station frequency, commute summaries, value context, provenance, freshness, duplicates, constraints, and explicit unknown fields.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	Yes	Two to eight listing IDs returned by a ChatHome search tool
`locale`	No	Response locale: en, fr, de, lu (Luxembourgish), pt (default: en; 'lb' is a deprecated alias for 'lu')

Output Schema

TableJSON Schema

Name	Required	Description	Default
`trust`	Yes
`listings`	Yes
`notFoundIds`	Yes
`schemaVersion`	Yes
`comparisonFields`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

addedOutput schema / properties / listings / items / properties / unknown

Added value: +{
+  "description": "Why each missingFields entry is unknown. not_in_search_result means get_listing may know it.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "field": {
+        "type": "string"
+      },
+      "reason": {
+        "enum": [
+          "not_stated",
+          "not_proven",
+          "conflicted",
+          "not_in_search_result"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "field",
+      "reason"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

AddedAug 31, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive safety properties. The description adds substantial response-content context—costs, availability, flood/noise checks, provenance, freshness, duplicates, explicit unknowns—which helps the agent understand what comes back and how normalized the comparison is.

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?

It is a single front-loaded sentence that begins with the core action and scope before listing response contents. The enumeration is dense but each item appears intended to signal comparison coverage rather than being outright filler.

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?

The definition is complete enough to call correctly: inputs are fully specified by the schema, safety annotations are present, and an output schema exists. The remaining gap is usage/routing guidance, but the purpose and response scope are otherwise well covered.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already fully documents both parameters, including the 2–8 ID bound and locale enum. The description reinforces the 2–8 listing range but adds no parameter meaning beyond that baseline.

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: 'Compare two to eight listings through one normalized AgentListing v2 response.' The multi-listing scope and explicit bounds distinguish it from single-listing siblings like get_listing and search tools.

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

Usage Guidelines2/5

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

The description implies use for comparing listings but gives no explicit when-to-use guidance, prerequisites, or alternatives. It does not say to prefer this over calling get_listing repeatedly or otherwise route the agent among siblings.

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

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

Need Help?