MCP Weather & Transit Advisor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LTA_ACCOUNT_KEY | No | Optional LTA DataMall AccountKey for live Singapore bus arrivals. Without a key, get_stop_departures falls back to Transitous timetables for Singapore stop codes. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geocode_locationB | Find the coordinates (latitude/longitude) of a city or town by name. Args: place: A city or town name, e.g. "Singapore" or "Austin". |
| get_current_weatherA | Get real-time weather for a city or town by name. Args: place: A city or town name, e.g. "Tokyo". |
| get_commute_adviceA | Plan a public-transport trip leaving now, using real timetables, and recommend an option based on the current weather. Uses open GTFS timetable data via Transitous (live delays where the operator publishes them). Coverage depends on the region. Args: origin: Where you start - a station, landmark or address, e.g. "Orchard MRT, Singapore". destination: Where you are going, e.g. "Changi Airport". |
| get_stop_departuresA | List upcoming buses/trains at a public-transport stop. For a Singapore 5-digit bus stop code (e.g. "83139") this returns LIVE arrivals from LTA DataMall when an LTA key is configured; otherwise it returns timetabled departures from Transitous. Args: stop: A stop name ("Tampines MRT, Singapore") or a Singapore 5-digit bus stop code ("83139"). limit: Maximum number of departures to list (default 8). |
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 4 tools
Each tool targets a distinct resource/action: coordinate lookup, current conditions, end-to-end commute planning, and stop-level departures. The two transit tools are clearly separated by scope (trip planning vs. a single stop's board), and geocode_location is explicitly a coordinate helper rather than a weather query.
All four names are snake_case verb_noun constructions (geocode_location, get_current_weather, get_commute_advice, get_stop_departures), with a consistent get_ prefix on the retrieval tools. No mixing of camelCase or vague single-word verbs.
Four tools is on the thin side but each one earns its place in a small weather+transit surface, with no filler or redundant tools. A forecast tool would round it out, but the count is well-scoped for the stated purpose.
Core workflows exist, but the weather side stops at 'current' with no forecast/hourly outlook, and commute advice is fixed to 'leaving now' with no departure-time or alternative-route parameter. There is also no reverse geocoding, leaving notable gaps for a server billed as a weather and transit advisor.