Commute lookup
commute_lookupCommute from one Chicago-area residential address to downtown Chicago on one service date: drive to a Metra station (without traffic), station buffer and scheduled train, for up to 5 station options (nearest stations first), with sources and a methodology link.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"service_date": "<service_date>"
},
"name": "commute_lookup"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Optional. Fill only with facts the user volunteered. No names, contact details or chat text. | |
| options | No | How many options to return, from 1 to 5, default 3. The nearest one or two stations are always included, so an answer can hold more options than requested. | |
| arrive_by | No | A clock time on the service date (H:MM, HH:MM, or HH:MM:SS in America/Chicago) or an RFC 3339 date-time with an offset, for example 09:00, 2026-11-12T09:00:00-06:00, or 2026-11-12T15:00:00Z. | |
| direction | No | ||
| window_id | No | ||
| address_id | No | ||
| components | No | ||
| terminal_id | No | ||
| address_text | No | ||
| depart_after | No | A clock time on the service date (H:MM, HH:MM, or HH:MM:SS in America/Chicago) or an RFC 3339 date-time with an offset, for example 09:00, 2026-11-12T09:00:00-06:00, or 2026-11-12T15:00:00Z. | |
| service_date | Yes | ||
| buffer_seconds | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||