Call it as explain_location on the Claro AI MCP server, https://platform.casafari.com/mcp/claro (how to connect).
Over REST: POST /v1/location (equivalent). MCP and REST compared.
What does Location figures do?
Footfall index (an index of pedestrian activity within a 5-minute walk that compares places with each other; not a head count, never people or visitors a day; split into weekday and weekend averages, morning/lunch/afternoon/evening and local/commuter/tourist shares of the index), residents within a 10-minute walk and drive (by age band 0-14, 15-29, 30-44, 45-59, 60+, with households, households per net income quintile and total spending power within a 10-minute walk), and nearby restaurants, fast food, cafes, shops, supermarkets, gyms and transit stops, for a premises id or any point (lat, lon) in Spain. Needs location data access on your account; a point that is not a premises is a live call on your account's location key (about 31 Location Intelligence operations per point). Returns location and location_sources: the same public field names, units and source notes as search_premises and get_premises (a 0 footfall or population is unknown, so null). figures is deprecated: same values as location under stored names; will be removed in a future version. A figure Location Intelligence has no data for is null, never 0.
Which parameters does explain_location take?
idstringlatnumberlonnumberlangstringen deHow do I call explain_location?
Required arguments only, with placeholder values. Your assistant fills them in from the parameters above.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "explain_location",
"arguments": {
"id": "…"
}
}
}