tokyo-transit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ODPT_API_KEY | Yes | Your ODPT API key from https://developer.odpt.org/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_routeA | 乗り換えルート検索 - 出発駅から到着駅までのルートを検索。日本語・英語・中国語自動識別、天候/高温/運休を検出しAIアドバイスを返答。 |
| get_station_infoC | 駅情報取得 - 駅の基本情報をODPT APIから取得。 |
| get_weatherB | 天気情報取得&多言語AIアドバイス - 気象庁APIから天気・気温を取得。高温時は熱中症注意を表示。 |
| list_ferry_portsA | フェリー/水上バス港一覧 - 東海汽船(伊豆諸島航路)と東京クルーズ(水上バス)の全港を表示。 |
| search_ferryA | フェリー/水上バス航路検索 - 港間の航路と時刻表を検索。 |
| list_transit_operatorsB | 交通事業者一覧 - 鉄道・AGT・モノレール・路面電車・フェリーの全事業者を種別フィルター付きで表示。 |
| get_operator_routesA | 事業者別路線一覧 - 指定事業者の全路線と駅を表示(例: tokyometro, jreast, mir, twr, yurikamome, toden)。 |
| search_fareA | 🚃 運賃検索 - 2駅間の運賃をODPTデータから検索します(東京メトロ・都営対応)。サーバー内で運賃を直接返すためYahoo依存不要。 |
| get_timetableA | 🕐 時刻表検索 - 指定駅の時刻表をODPTデータから検索します。Yahooに依存せず直接時刻を提供。 |
| search_busA | 🚌 バス路線検索 - 都営バスの路線・バス停情報をODPTデータから検索します。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes, such as route search, fare search, timetable lookup, and station info. Slight overlap exists between search_route and get_weather since both provide weather-related AI advice, but they serve different primary intents. The ferry listing vs. route search tools are also clearly separated.
All tool names follow a consistent verb_noun pattern using snake_case, with verbs like search, get, and list. This creates a predictable and uniform naming convention across the entire set.
With 10 tools, the server is well-scoped for a comprehensive Tokyo transit system, covering route planning, fares, timetables, ferries, buses, operators, and weather. Each tool serves a distinct functional area without unnecessary redundancy.
The tool set covers core transit needs well: route search, fares, timetables, station info, operators, ferries, and buses. Minor gaps include lack of real-time disruption alerts as a dedicated tool, though search_route partially detects suspensions. Missing line-specific station lists are handled via get_operator_routes.