odpt-mcp

get_bus_route

Read-onlyIdempotent

List stops along a Toei bus route pattern by supplying a pattern ID from bus stop searches or timetables. Retrieve ordered route stops with limit and offset pagination.

Instructions

List stops along a Toei bus route pattern from search_bus_stops or its timetable.

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": {
      "pattern_id": "<pattern_id>"
    },
    "name": "get_bus_route"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`pattern_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond that — nothing about pagination limits (default 10, max 50), result ordering, or the Toei-only scope constraint, which the pattern regex enforces but the prose never mentions.

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

Conciseness4/5

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

One sentence with no filler, and the core action is front-loaded. The dangling "or its timetable" clause adds ambiguity rather than information, which is the only real cost.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and annotations cover safety. However, for a paginated list tool with three parameters at 0% schema description coverage, the description leaves pagination behavior and the Toei-only id constraint unstated.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning and it does not. It vaguely gestures at a "Toei bus route pattern" matching pattern_id, but limit and offset are entirely undocumented in prose, leaving an agent to infer pagination from the schema's defaults alone.

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

Purpose4/5

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

States a specific verb and resource: "List stops along a Toei bus route pattern." That distinguishes it from timetable and fare siblings. The trailing clause "from search_bus_stops or its timetable" is ambiguous about whether it describes the id source or the returned content, which keeps it from a 5.

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 a usable prerequisite by naming search_bus_stops as where the route pattern comes from, which tells an agent the call is downstream of a stop search. It does not state any when-not condition or contrast with get_bus_stop_timetable, so the guidance is clear but not complete.

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

Deploy Server