routes_directions

The turn-by-turn route between two places, with the distance for each instruction. Use ETA instead when only the travel time is wanted — this asks the provider for more and costs more

3 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 the journey starts, e.g. 'King's Cross, London' (or give from_lat/from_lon)
`to`	string	Where the journey ends, e.g. 'Heathrow Airport'
`from_lat`	number	Optional start latitude, if already known
`from_lon`	number	Optional start longitude, if already known
`to_lat`	number	Optional end latitude, if already known
`to_lon`	number	Optional end longitude, if already known
`mode`	string	How to travel: drive (default), walk, cycle or transit
`depart_at`	string	When the journey starts, as RFC3339. Defaults to now
`arrive_by`	string	Be there by this time, as RFC3339. Cannot be combined with depart_at

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":{},"name":"routes_directions"}}

Try it in the playground.