onebusaway-mcp-server

Get Stop Context

onebusaway_get_stop_context

Read-only

Everything happening at a stop in one call: the stop's details, its real-time arrivals, and full detail for every service alert on the stop or on any arrival in the window. Returns what onebusaway_get_stop, onebusaway_get_arrivals, and one onebusaway_get_alert call per alert would, from a single upstream request — arrivals in the onebusaway_get_arrivals shape, alerts in the onebusaway_get_alert shape. The stop omits its served-route list; use onebusaway_get_stop for routeIds. Stop IDs use agency-prefixed format: {agencyId}_{localId} (e.g. "1_75403").

Input Schema

TableJSON Schema

Name	Required	Description
`stopId`	Yes	Agency-prefixed stop ID (e.g. "1_75403" for Metro Transit stop 75403). Use onebusaway_find_stops or onebusaway_search_stops to discover IDs.
`minutesAfter`	No	Include arrivals expected within the next N minutes — an integer from 0 to 240. Defaults to 35. For a longer horizon, use onebusaway_get_schedule_for_stop.
`minutesBefore`	No	Include arrivals that departed up to this many minutes ago — an integer from 0 to 60. Defaults to 5.

Output Schema

TableJSON Schema

Name	Required	Description
`stop`	No	The queried stop, without its served-route list (use onebusaway_get_stop for routeIds). Null when the upstream response omitted the stop.
`error`	No	Present when the call failed. Absent on success.
`alerts`	No	Service alerts on this stop or on any arrival in the window, each listed once — including alerts whose affected arrivals fall outside the window.
`notice`	No	What the response is missing and where to get it — no arrivals in the window, stop details absent, or referenced alerts absent.
`arrivals`	No	Arrivals and departures at this stop within the requested time window.
`currentTime`	No	Server time as Unix milliseconds, for computing countdown timers.
`queriedStop`	No	Stop ID queried.
`windowMinutes`	No	Time window used for the arrivals query.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 25, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint annotation already signals safety, so the description correctly focuses on additional behavioral context: the single upstream request, the response shapes matching get_arrivals and get_alert, and the deliberate omission of routeIds. This goes beyond the annotation without contradicting it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact but information-dense: the main promise is front-loaded, then response shapes and exclusions follow in three purposeful sentences. No sentence is redundant or wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a multi-purpose aggregate tool, the definition covers what it returns, how results are shaped, what it omits, ID format, and relevant alternatives. Output schema and readOnlyHint fill the remaining context, and required parameter handling is fully specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with clear descriptions, defaults, ranges, and discovery hints already on stopId, minutesAfter, and minutesBefore. The description adds an ID format reminder and points to sibling tools, but most parameter meaning is already carried by the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource and operation: a single call that returns stop details, real-time arrivals, and full service alerts. It explicitly contrasts itself with onebusaway_get_stop, onebusaway_get_arrivals, and onebusaway_get_alert, so an agent can distinguish this aggregate from its siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states the intended use case ('Everything happening at a stop in one call') and gives an explicit exclusion: the stop omits routeIds, so use onebusaway_get_stop for that. The minutesAfter parameter schema additionally routes longer-horizon needs to onebusaway_get_schedule_for_stop, making alternatives and conditions clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All onebusaway-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.