Skip to main content
Glama

onebusaway-mcp-server

by io.github.cyanheads

Get Stop Details

onebusaway_get_stop
Read-only

Fetch details for a specific stop by ID. Returns the stop's name, coordinates, direction, served routes, and wheelchair accessibility. Stop IDs use agency-prefixed format: {agencyId}_{localId} (e.g. "1_75403" for Metro Transit stop 75403).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stopIdYesAgency-prefixed stop ID (e.g. "1_75403" for Metro Transit stop 75403, "40_100239" for Sound Transit). Use onebusaway_find_stops or onebusaway_search_stops to discover IDs.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAgency-prefixed stop ID.
latNoLatitude of the stop.
lonNoLongitude of the stop.
codeNoThe stop code printed on the sign.
nameNoStop name.
errorNoPresent when the call failed. Absent on success.
routeIdsNoIDs of routes that serve this stop. Use with onebusaway_get_arrivals or onebusaway_get_schedule_for_stop.
directionNoCompass direction of travel at this stop (e.g. "NW").
wheelchairBoardingNoWheelchair boarding status.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint: true, so the description is not required to state that. It adds value beyond the annotation by enumerating the returned fields and explaining the ID format, giving the agent concrete expectations for the operation's behavior. No contradictions with annotations.

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, zero waste. The action and output summary are front-loaded, followed by the essential ID format detail. Every word earns its place; no redundant qualifiers or filler.

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 single-parameter read-only tool with a complete schema description and output schema present, the description covers everything an agent needs: what the tool does, what it returns, and how to construct the ID. Nothing essential is missing given the low complexity and available structured data.

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

Parameters4/5

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

Schema description coverage is 100%, so the parameter is already documented. The description and parameter text add extras: the agency-prefixed format with examples and pointers to discovery tools, which are not present in the bare schema. This meaningfully enhances understanding of how to fill the parameter correctly.

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 clearly states the action ('Fetch details') and the resource ('a specific stop by ID'), lists the returned fields (name, coordinates, direction, served routes, wheelchair accessibility), and differentiates from sibling tools by focusing on a single stop's details rather than schedules, arrivals, or routes.

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

Usage Guidelines4/5

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

It gives clear context that this tool is for fetching stop details, and the parameter schema advises using onebusaway_find_stops or onebusaway_search_stops to discover IDs. It does not explicitly contrast with other 'get' siblings like get_schedule_for_stop, but the purpose is unambiguous enough for correct selection.

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