tdx-taiwan-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TDX_CLIENT_ID | Yes | TDX API key Client Id | |
| TDX_MAX_ITEMS | No | Most items any tool returns | 200 |
| TDX_CLIENT_SECRET | Yes | TDX API key Client Secret | |
| TDX_REQUESTS_PER_SECOND | No | Client-side rate limit; match it to your TDX plan (`0` turns it off) | 5 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| youbike_nearbyA | YouBike / Moovo stations nearest to a coordinate, with live bikes (regular and e-bike) and empty docks, nearest first. Example: lat 25.0478, lon 121.517, city "Taipei". |
| youbike_stationA | YouBike / Moovo stations whose name or address contains a keyword (Chinese or English), with live bikes and empty docks. Example: city "Taipei", keyword "臺北車站". |
| cycling_routesA | Cycle paths (自行車道) of a city: name, district, the roads where each starts and ends, length and its end points; near a coordinate (nearest first) or by a keyword in the name, road or district. Example: city "Taipei", keyword "河濱"; or lat 25.0478, lon 121.517, city "Taipei". |
| bus_stops_nearbyA | Bus stops nearest to a coordinate, each with its heading and the city bus and InterCity coach routes that stop there, nearest first. Pass a stop and route to bus_eta for live arrivals. Example: lat 25.0478, lon 121.517, city "Taipei". |
| bus_route_searchA | Bus routes whose name, or first or last stop, contains a keyword, with their endpoints, operators and fare. Use it to find the exact route name the other bus tools need. Example: city "Taipei", keyword "307"; or city "InterCity", keyword "1610". |
| bus_route_stopsB | The stops of a bus route in order, for each direction and sub-route. Example: city "Taipei", routeName "307", direction "outbound". |
| bus_etaA | Live estimated arrival of the next buses at the stops of a route ("4 min", "arriving now", "last bus has passed"), with the minutes to the buses after it and, in cities that publish their fleet, whether the coming bus is low-floor with a wheelchair ramp. Give stop to see one stop only. Example: city "Taipei", routeName "307", stop "西門". |
| bus_positionsA | Where the buses on a route are right now: position, speed, direction and status of each vehicle, whether it is low-floor with a ramp (where the city publishes its fleet), and the stop each one last arrived at or left. Example: city "Taipei", routeName "307". |
| bus_stop_arrivalsA | Every bus due at one stop, all routes at once, soonest first: minutes to arrival, where each bus is heading, and the buses after it. Give the stationUID from bus_stops_nearby, or the stop name. Example: city "Taipei", stationUID "TPE1895"; or city "Taipei", stop "臺北車站(鄭州)". |
| bus_timetableA | Scheduled departures of a bus route on a day, from its first stop or a given stop, or how often it runs for routes run by frequency. Use it for planning ahead and for coaches and rural routes; use bus_eta for live arrivals. Kaohsiung publishes no timetables. Example: city "InterCity", routeName "1610", stop "臺北轉運站". |
| bus_alertsA | Current and upcoming bus detours, suspensions, moved stops and extra services in a city or on the InterCity coaches, with the routes and stops they affect, plus the latest operator news. Example: city "Taipei"; or city "Taipei", route "307". |
| bus_fareA | What a bus route costs, per passenger type and ticket (cash single ticket, smart card such as EasyCard): the fare between two stops for coaches and routes priced by distance, or the fare per section for city routes. Example: city "InterCity", routeName "1610", from "臺北", to "高雄"; or city "Taipei", routeName "307". |
| bus_first_lastA | When the first and the last bus of a route leave on a day, per direction and sub-route. Taipei, New Taipei and Tainan publish no first/last list, so there it is worked out from the timetable. Example: city "Taichung", routeName "300"; or city "InterCity", routeName "1610". |
| thsr_timetableA | THSR (高鐵) trains from one station to another on a day, with departure, arrival and travel time, from now on for today. TDX covers about four weeks ahead. Example: from "台北", to "左營", date "2026-10-23", after "08:00". |
| thsr_seatsA | Reserved-seat availability (available, limited, sold out) in standard and business class for THSR trains between two stations, with their times. Updated about every 10 minutes. Example: from "台北", to "台中". |
| thsr_fareA | THSR single-journey fares between two stations in NT$, per car (standard, business, non-reserved) and passenger type (adult, child, senior, ...). Example: from "台北", to "台南". |
| thsr_trainA | Every stop of one THSR train on a day, with arrival and departure times. Example: trainNo "0803" (or "803"). |
| tra_timetableA | TRA (臺鐵) trains from one station to another on a day: train type, departure, arrival, travel time, from now on for today. TDX covers about two months ahead. Example: from "臺北", to "花蓮", date "2026-10-23". |
| tra_live_boardA | Trains about to arrive at or leave a TRA station now, with delay and platform. Only imminent trains are listed; use tra_timetable for later ones. Example: station "板橋". |
| tra_trainA | One TRA train today: its stops with times, and where it is now and how late it runs. Example: trainNo "123". |
| tra_fareA | TRA single-journey fares between two stations in NT$ per train type (自強, 莒光, 區間, ...) and passenger type, with the distance. Example: from "臺北", to "高雄". |
| metro_live_boardA | Minutes until the next metro trains at a station, per line and destination. KRTC, TYMC and KLRT list every station; TRTC (Taipei) only lists trains arriving right now, so an empty Taipei board is normal. Example: system "KRTC", station "美麗島". |
| metro_fareA | Metro single-journey fares between two stations in NT$, per passenger type, with the distance. Example: system "TRTC", from "台北車站", to "淡水". |
| metro_frequencyA | How often metro trains run on each line through the day (minutes between trains, peak and off-peak) and its operating hours, for a day of the week. Covers the Taipei Wenhu line (文湖線), which has no timetable. Example: system "TRTC", line "BR". |
| metro_first_last_trainA | First and last train times at a metro station for each line and direction. Example: system "TRTC", station "台北車站". |
| metro_travel_timeA | How long a metro journey takes between two stations, with the line changes: each leg with its line, direction (toward) and stops, the walking time at each change, how often trains run now and the expected wait. TRTC covers Taipei and New Taipei (including the Circular line); also Kaohsiung, Taichung and the Taoyuan airport line (express and local). Example: system "TRTC", from "台北車站", to "台北101/世貿". |
| afr_fareA | Alishan Forest Railway (阿里山林業鐵路) single-journey fares in NT$ between two stations, per train type and passenger type, with the distance. Example: from "嘉義", to "奮起湖". |
| afr_timetableA | The regular timetable of the Alishan Forest Railway (阿里山林業鐵路): every train, or the trains from one station to another with their times. Services change with the season and weather; the result says when to check the official site. Example: from "嘉義", to "奮起湖". |
| rail_station_searchA | Stations of a rail system by name (Chinese or English) or nearest to a coordinate, with their IDs. The other rail tools accept names directly, so use this to explore, to find the nearest station, or when a name is ambiguous. Example: system "TRTC", lat 25.0478, lon 121.517; or system "TRA", keyword "新竹". |
| rail_alertsA | Current service status and disruption alerts of THSR, TRA or a metro system ("normal" when everything runs). Example: system "TRA". |
| rail_station_departuresA | A station's departures on a day toward every destination, from its timetable: TRA, THSR or a metro (including Taipei Metro, whose live board shows arrivals only). Use tra_timetable or thsr_timetable for trains between two stations. Example: system "TRA", station "板橋"; or system "TRTC", station "台北車站", toward "淡水". |
| rail_station_infoA | Exits of a TRA, THSR or metro station with where they come out and whether they have stairs, an escalator or a lift, plus where its lifts, toilets and information desks are. Give the coordinates of where you are going to sort the exits by distance. Example: system "TRTC", station "台北101/世貿", lat 25.0336, lon 121.5648. |
| flight_statusA | Live status of a flight to or from Taiwan: scheduled, estimated and actual times, delay, terminal, gate and status (on time, delayed, departed, cancelled, ...). TDX lists flights around today. Example: flight "CI100"; or "B7 8751". |
| flight_boardA | An airport's live departure or arrival board for passenger flights: times, delay, status, terminal and gate, from an hour ago on for today, with the current weather. Covers the Taiwan airports. Example: airport "TSA", direction "departures", otherAirport "金門". |
| flight_scheduleA | Scheduled flights between two airports on a day. Between Taiwan airports: the domestic flights of Mandarin Airlines, UNI Air and Daily Air with cancellations and fares in NT$. To or from abroad: the published international timetable, code-share numbers grouped under one flight. Use flight_status or flight_board for live status. Example: from "松山", to "金門", date "2026-11-02"; or from "TPE", to "NRT". |
| flight_seatsA | Whether seats are left on a domestic flight of Mandarin Airlines (AE), UNI Air (B7) or Daily Air (DA): available, fewer than 5 left, or sold out, per cabin when the airline says. TDX asks the airline live, so this can take up to 30 s, and UNI Air allows few requests; call it for one flight at a time. Example: flight "AE1273", date "2026-11-02". |
| ferry_timetableA | Ferry sailings from one port to another on a day, with times and, for today, live status (on time, departed, cancelled) and service alerts such as typhoon suspensions. Example: from "富岡", to "綠島"; or from "馬公", to "七美", city "PenghuCounty". |
| ferry_live_boardA | A ferry port's live departures and arrivals for today: scheduled, estimated and actual times, vessel and status (on time, departed, cancelled with the reason). About 25 ports have a board (小琉球, 東港, 綠島, 富岡, 南竿, 金門水頭, ...); use ferry_timetable for the others. Example: port "小琉球". |
| ferry_fareA | Ferry fares in NT$ between two ports, per route, ticket, cabin and passenger type. Example: from "基隆", to "南竿". |
| ferry_alertsA | Current ferry service alerts: suspensions for typhoons or rough seas, cancelled or changed sailings, with the routes and ports they affect. Example: keyword "綠島"; or no input for every alert. |
| ferry_positionsA | Where ferries and other passenger vessels around Taiwan are right now (AIS): position, speed, course, status (under way, moored, ...) and the nearest port. Search by vessel name, near a port, or near a point. Positions are not tied to routes, and names are as the ships broadcast them (often English). Example: port "小琉球"; or keyword "TAIMA". |
| traffic_liveA | Live speed and congestion of road sections on the national freeways, provincial highways or a city’s roads, most congested first, with a count of sections per congestion level. Freeway sections are named after interchanges, so search them by keyword; city sections can also be searched by lat/lon. Example: network "freeway", keyword "林口"; or network "Taipei", lat 25.0478, lon 121.517. |
| traffic_eventsA | Current road events: accidents, roadworks, congestion, traffic control and weather closures, plus announced events (parades, planned works) for cities and provincial highways, with where they are and how much they block. Example: network "freeway", type "accident"; or network "Taipei", lat 25.0478, lon 121.517. |
| traffic_camerasA | Live traffic cameras on the national freeways, provincial highways or a city’s roads, by road, place or distance, with the link to each live stream (open it to watch; TDX gives no still images). Example: network "freeway", keyword "林口"; or network "Taipei", lat 25.0478, lon 121.517. |
| traffic_signsA | What the changeable message signs over the national freeways, provincial highways or a city’s roads show right now: travel times to the next interchanges, congestion, incidents and roadworks warnings. Example: network "freeway", keyword "汐止", direction "S". |
| traffic_travel_timeA | How long a car takes right now between two national freeway (國道) interchanges, from live eTag gantry times: the fastest route, its distance and average speed, and the time and speed of each segment so slow stretches stand out. Example: from "林口", to "新竹". |
| parking_nearbyA | Car parks and on-street parking nearest to a coordinate, with free spaces right now for cars or scooters, fare and opening status, nearest first. Coverage differs per city (NewTaipei has on-street parking only). Example: lat 25.0478, lon 121.517, city "Taipei". |
| parking_searchB | Car parks and on-street parking whose name, address or road contains a keyword, with free spaces right now. Example: city "Taipei", keyword "市府"; or keyword "復興北路". |
| ev_charger_nearbyA | EV charging stations nearest to a coordinate, with their connectors (type, AC/DC, power) and how many are free, in use or out of order right now, plus opening hours and prices. Use city "freeway" for the freeway service areas. Example: lat 25.0478, lon 121.517, city "Taipei", connector "CCS2". |
| tdx_getA | GET any TDX API path (https://tdx.transportdata.tw/api-service/swagger) with OData options. Use it only when no specific tool covers the data. Field names in filter, select and orderBy are TDX field names (e.g. StationName/Zh_tw). Results are not cached and null or empty fields are dropped. Example: path "/v2/Rail/THSR/Station", select ["StationID","StationName"], top 5. |
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 50 tools
Tools are mostly distinct by transport mode and action, and descriptions clarify live vs scheduled vs station vs route. Some subtle overlaps remain, such as bus_stop_arrivals vs bus_eta, rail_station_departures vs mode-specific timetables, and flight_status vs flight_board, so an agent could occasionally misselect among the 50.
All names use snake_case and a predictable domain-prefix plus descriptor pattern (bus_*, thsr_*, metro_*, traffic_*). Minor inconsistencies include singular/plural variation (bus_stops_nearby vs bus_stop_arrivals), noun vs action suffixes, and the generic tdx_get outlier.
50 tools is heavy, but the server covers a genuinely broad multi-modal transport domain, so many tools are justified. Still, the count is unwieldy and several mode-specific tools could be consolidated or grouped to reduce selection load.
Coverage is extensive across buses, rail, metro, ferries, flights, traffic, parking, EV charging, and bike share, including live data, timetables, fares, alerts, and station information. The main gap is integrated cross-modal journey planning/trip routing; tdx_get helps fill obscure data gaps but not complex workflows.