Nagoya Bus 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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_station_numberA | Get station number for a given station name using fuzzy matching. Attempts exact match first, then falls back to fuzzy matching with 60% similarity threshold if no exact match is found. |
| get_timetableB | Get formatted timetable information for all routes at a station. Retrieves and formats timetable data including routes, directions, boarding locations, and departure times organized by day of week. |
| get_approach_for_routeA | Get real-time bus approach and position information for a route. Provides both historical data (latest bus passages at stops) and current position data for buses actively running on the route. |
| get_approach_for_stationA | Get real-time bus approach information for all routes at a station. Provides a list of routes that currently have activity at the specified station (either a recent passage time or at least one approaching bus), along with a URL for more details. Routes that have neither a latest pass time nor any approaching buses are filtered out and are not included in the result. The remaining routes are sorted by the proximity of their approaching buses so that routes with the nearest approaching vehicles appear first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| ask_timetable | Ask for the timetable of a bus station on a specific date. |
| ask_bus_approach | Ask for the bus approach information at a bus station. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct operation: route-level approach, station-level approach, station number lookup, and timetable retrieval. No overlap in purpose.
All tools follow a consistent 'get_X_for_Y' pattern with clear verb_noun structure, using snake_case throughout.
4 tools is slightly low but acceptable for a focused bus information server. Each tool serves a clear purpose without being redundant.
Missing tools to list available routes or stations, which may create dead ends for agents that don't know route or station names in advance. Core real-time and timetable queries are covered.