openbusdata

get_route_stops

Retrieve the complete list of stops for any bus route by specifying operator and route number, with optional direction filter to get inbound or outbound stops.

Instructions

Get the full ordered list of stops for a specific bus route.

Parameters: operator: Operator name (exact or partial match). route: Route number/identifier. direction: Optional filter: 'inbound', 'outbound', or leave blank for all.

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": {
      "operator": "<operator>",
      "route": "<route>"
    },
    "name": "get_route_stops"
  }
}

Input Schema

Name	Required	Description	Default
`route`	Yes
`operator`	Yes
`direction`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Jul 6, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states that the tool returns a 'full ordered list of stops', but does not mention it is read-only, whether it requires authentication, data freshness, or any side effects. The behavioral disclosure is insufficient.

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 concise: a single sentence for the main purpose followed by a bullet list of parameters. It is front-loaded with the core function and contains no unnecessary words.

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

Completeness4/5

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

An output schema exists, so the description does not need to detail return values. It covers the main input parameters and the output concept ('full ordered list'). However, it does not address edge cases like missing routes or invalid operator names, which would be helpful.

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 0%, so the parameter descriptions add vital meaning. The description explains that 'operator' supports exact or partial match, 'route' is a number/identifier, and 'direction' accepts specific values ('inbound', 'outbound') or null for all. This exceeds the schema's basic type info.

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 verb 'Get' and the resource 'full ordered list of stops for a specific bus route'. It distinguishes itself from sibling tools like 'find_buses_by_arrival_time' and 'get_live_buses_on_route' by focusing on stops along a route.

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

Usage Guidelines3/5

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

The description implies when to use the tool (to get stops for a route) but provides no explicit guidance on when not to use it or alternatives. It mentions optional direction filtering but no context about when to prefer this over other similar tools.

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

Deploy Server