Commute lookup, batch
commute_lookup_batchThe same dated commute as commute_lookup for up to 10 Chicago-area addresses in one call, for comparing homes. Returns one result per address in request order; an address that cannot be answered gets its own error entry and the others still answer. Default 1 option per address.
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>",
"addresses": "<addresses>"
},
"name": "commute_lookup_batch"
}
}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 | Options per address, from 1 to 3, default 1. The nearest one or two stations are always included, so an answer can hold more options than requested. | |
| addresses | Yes | ||
| 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 | ||
| terminal_id | 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 | |||