japan-transit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| suggest_placesB | Search Japanese stations, stops, facilities, and addresses. Use the returned endpoint field with plan_route or guidance_plan. |
| suggest_stationsA | Search station/stop IDs by multilingual prefix. Use returned station ids with route planning. |
| reverse_placesC | Find nearby stations, stops, places, or addresses for a map coordinate. |
| plan_routeB | Search transit routes in Japan for departure, arrival, first train, or last train. Times are seconds from service-date midnight in the response timezone. |
| guidance_planC | Search ranked transit guidance options with comparison metrics, strategy, tracking, evidence, and map geometry. |
| get_stationB | Get station details, platforms, and serving routes. |
| station_departuresC | Get a station departure board where the source data license permits this presentation. |
| list_feedsA | List ingested transit feeds with license attribution. |
| list_operatorsB | List operator branding marks and logo/data license metadata. |
| healthA | Check Transit API liveness. |
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 distinct purposes, but plan_route and guidance_plan both involve transit planning with overlapping functionality, potentially causing selection confusion.
Naming mixes verb_noun (get_station, list_feeds) and noun_noun (guidance_plan, station_departures) conventions, lacking a consistent pattern.
10 tools is well within the ideal range for a transit MCP server, covering essential operations without being excessive.
Covers core transit planning and station info, but lacks real-time alerts or fare details, leaving minor gaps in typical use cases.