Find Transit Stops
transit_find_stopsFind stop codes for a transit agency by matching stop names, enabling subsequent real-time departure queries.
Instructions
Find an agency's stops by name, and get the stop codes the real-time tools need.
This is the bridge between "Downtown Berkeley" and the code transit_next_departures wants. Pass a query: a large agency has thousands of stops, and 511 returns all of them in one unpaginated response.
Args:
operator_id (string): agency code from transit_list_operators
query (string): substring match on the stop name — strongly recommended
limit (number): maximum stops to return (default: 25)
response_format ('markdown' | 'json'): output format (default: 'markdown')
Returns: { "count": number, "total": number, "truncated": boolean, "stops": [ { "id": string, "Name": string, "Location": { "Latitude": string, "Longitude": string } } ] }
Examples:
"When's the next train from Downtown Berkeley?" -> operator_id='BA', query='downtown berkeley', then pass the id to transit_next_departures
"Find Muni stops on Judah" -> operator_id='SF', query='judah'
Don't use when: you already have the stop code
Error Handling:
Stop codes belong to ONE operator and are not interchangeable between agencies
Filtering happens on this server, so a narrow query does not save quota — the full list is fetched either way
511 allows 60 requests per hour across ALL endpoints
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum results to return (max 200) | |
| query | No | Case-insensitive substring match on the stop name. Strongly recommended — a large agency has thousands of stops | |
| operator_id | Yes | Operator code from transit_list_operators, e.g. 'BA' for BART, 'SF' for Muni | |
| response_format | No | Output format: 'markdown' for human-readable, 'json' for machine-readable | markdown |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | ||
| stops | Yes | ||
| total | Yes | ||
| truncated | Yes |