routes_nearest
routes_nearest
Given a starting point and several destinations, say which is quickest to reach and put them in order. Each destination is a separate routing lookup, so ask about the places you are actually choosing between rather than a long list
2 credits per call, from your balance — or paid per request in USDC with no account at all.
Runs on Routes — How to get from one place to another — time, traffic and turn-by-turn.
Arguments
| Name | Type | What it is |
|---|---|---|
from | string | Where you are starting from, e.g. 'Shoreditch, London' (or give from_lat/from_lon) |
from_lat | number | Optional start latitude, if already known |
from_lon | number | Optional start longitude, if already known |
to* | array | The places to compare, e.g. ['Heathrow', 'Gatwick', 'Stansted'] |
mode | string | How to travel: drive (default), walk, cycle or transit |
Calling it
Three doors onto the same method. MCP is what an agent speaks, REST is what a program speaks, and the answer is identical.
{"id":1,"jsonrpc":"2.0","method":"tools/call","params":{"arguments":{"to":"to"},"name":"routes_nearest"}}Try it in the playground.


