Yatmo MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LicenceKey | Yes | Your Yatmo backend key, sent in the `LicenceKey` header (`LicenseKey` is also accepted). Get a key at https://yatmo.com. The key grants access to your Yatmo account, so keep it in the client's secret store. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yatmo_get_location_summaryA | Returns a human-readable neighbourhood summary plus structured facts (nearest school, nearest supermarket, public transport) around a property location. Use this to explain why a property is well situated. |
| yatmo_get_nearby_poisB | Lists points of interest around a property, optionally filtered by category, within a radius. Categories: school, nursery, supermarket, public_transport, train_station, motorway. 'school' returns actual schools (excluding daycare); 'nursery' returns crèches/daycare only. |
| yatmo_get_nearest_by_categoryA | Returns the single nearest point of interest of a given category (e.g. the nearest school) with distance and travel time. Categories: school, nursery, supermarket, public_transport, train_station, motorway. |
| yatmo_get_accessibility_profileA | Returns a synthetic accessibility view of a property: public-transport presence and nearest stop distance. Use it to answer questions like 'is this property practical without a car?'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The four tools overlap substantially: yatmo_get_location_summary already reports nearest school, supermarket, and public transport, which duplicates what yatmo_get_nearest_by_category returns, and yatmo_get_accessibility_profile re-covers public-transport/nearest-stop data. Descriptions do clarify the granularity (aggregated summary vs. list vs. single nearest vs. derived accessibility view), so an agent can mostly choose correctly, but the boundaries are fuzzy.
All tools follow a strict 'yatmo_get_<noun>' snake_case pattern (get_location_summary, get_nearby_pois, get_nearest_by_category, get_accessibility_profile). The verb and namespace prefix are uniform throughout with no deviation.
Four tools is a tight but sensible scope for a neighbourhood/property-location service, and each tool maps to a distinct query granularity. It is on the lean side, but no tool feels redundant enough to be dead weight.
The surface covers the core location workflows: aggregate summary, filtered POI listing, single nearest POI with distance/travel time, and an accessibility view. Minor gaps exist (e.g., no batch/multi-category query or distance/commute matrix), but agents can compose the existing tools to cover most questions.