Implementation guide · MCP
Connect a property assistant
to neighbourhood facts.
Keep the listing, the location data and the generated answer distinguishable. That makes the answer easier to check and the integration easier to debug.
Connect
Use the documented client configuration.
A read-only location service.
Connect your MCP-compatible client using the Yatmo endpoint and licence header. Keep the key in the client’s secure configuration.
MCP quick starthttps://mcp.yatmo.com/mcp/v1
Header: LicenceKey: YOUR_KEYMCP uses “LicenceKey”; the REST API uses “LicenseKey”. Follow the reference for the interface you connect.
Call
Ask one precise question.
Question
Is there a school near this property?
The listing supplies the coordinates. The tool supplies the nearby-place facts.
yatmo_get_nearest_by_category
{
"latitude": 50.846714,
"longitude": 4.352514,
"country": "BE",
"language": "en",
"category": "school"
}Interpret
Carry the units into the answer.
Published response example · Brussels
Cefa – Centre Scolaire Eperonniers-Mercelis
- Distance
- 363 metres
- Travel time
- 3 minutes
- Mode
- Cycling
Do not describe the cycling time as a walking time. If the question requires a specific journey, request the corresponding route.
Recorded example from Yatmo’s existing MCP guide, not a live tool call.
Handle the missing result
No fact means no invented answer.
If no place is returned, explain that the requested information is unavailable. Do not turn that into a universal claim about the neighbourhood.
Query the properties consistently and make the comparison criteria visible. Any weighting is a choice made by your product.
Keep the catalogue context, tool result and assistant output identifiable in your own integration logs.