Skip to main content
Glama

onebusaway-mcp-server

by io.github.cyanheads

Get Stop Schedule

onebusaway_get_schedule_for_stop
Read-only

Full-day departure schedule for a stop. Lists every departure by route and direction for the specified date (defaults to today). Useful for planning or when real-time data isn't needed. For live predictions, use onebusaway_get_arrivals instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoISO 8601 date (e.g. "2026-05-23"). Defaults to today in the agency's timezone.
stopIdYesAgency-prefixed stop ID (e.g. "1_75403"). Use onebusaway_find_stops or onebusaway_search_stops to discover IDs.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate parameter used for the schedule request, if specified.
errorNoPresent when the call failed. Absent on success.
noticeNoGuidance when no routes were found — e.g. no service on weekends or holiday schedule in effect.
routesNoAll routes with departures from this stop on this date.
stopIdNoThe queried stop ID.
stopNameNoStop name.
routeCountNoNumber of routes with departures from this stop on this date.
queriedStopNoStop ID queried.
serviceDateMsNoService date as Unix milliseconds (start of service day).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description does not contradict this. It adds meaningful behavior beyond the annotation: the full-day scope, defaulting to today in the agency's timezone, and listing by route and direction. This enriches the operational picture without being verbose.

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?

Two sentences plus a routing sentence, with the core purpose front-loaded. Every sentence earns its place; no fluff. The structure is ideal for quick parsing by an agent.

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?

With an output schema present and full parameter documentation, nothing is missing for correct invocation. The description covers the functional scope, the date default, and the alternative for live data. This is complete for a read-only schedule lookup tool.

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% — both parameters (stopId, date) are documented in the schema. The description adds no extra parameter-level detail beyond the schema, so the baseline 3 applies. It provides no additional syntax or edge-case guidance beyond what the schema already covers.

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 states a specific verb and resource ('full-day departure schedule for a stop') and explicitly differentiates itself from the sibling onebusaway_get_arrivals by noting the alternative for live predictions. An agent can immediately tell what this tool does and how it differs from nearby options.

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?

It provides clear guidance on when to use this tool ('for planning or when real-time data isn't needed') and when not to, explicitly naming the alternative (onebusaway_get_arrivals). This is model routing guidance.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Every tool targets a distinct operation: find_* for location-based search, search_* for text-based search, get_* for fetching by ID, list_* for enumeration, and get_arrivals for real-time vs get_schedule_for_* for scheduled data. Even similar pairs like find_routes/search_routes are clearly differentiated by their search mode.

Naming Consistency5/5

All tools follow a uniform `onebusaway_` prefix followed by a consistent verb pattern: find (location search), search (text search), get (retrieve by ID), list (enumerate), plus specific get_schedule_for_route/stop. Naming is entirely snake_case and logically structured.

Tool Count5/5

15 tools cover the full scope of a transit API without bloat: discovery (find/search), details (get), enumeration (list), real-time (arrivals/vehicles/trip), schedules, and alerts. Each tool serves a distinct purpose and fits within a typical well-scoped server.

Completeness5/5

The surface covers the primary travel workflows: finding routes/stops by location or name, retrieving full details, real-time arrivals/trip/vehicle tracking, scheduled departures for both routes and stops, service alerts, and agency enumeration. There are no obvious dead ends; each lookup provides IDs for follow-up queries.

Resources