Schema | japan-transit-mcp

japan-transit-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Anchovy-s3/japan-transit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server