mcp-hsl
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DIGITRANSIT_SUBSCRIPTION_KEY | Yes | Your free Digitransit subscription key. Get it from https://portal-api.digitransit.fi/ |
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 |
|---|---|
| geocodeA | Look up coordinates for an address, place, or landmark in the Greater Helsinki area. Returns up to 10 candidates with Finnish and Swedish names, coordinates, and a confidence score. Use this before plan_journey when you only have a place name. |
| stop_departuresA | Get the next departures from a Helsinki public-transport stop, including real-time delays. Accepts either a stop name (e.g. 'Kamppi', looked up internally) or an HSL stop ID (e.g. 'HSL:1140447'). If the name matches multiple stops, returns the candidate list so the caller can pick one. |
| plan_journeyA | Plan a public-transport journey between two places in Greater Helsinki. Accepts place names or addresses; both endpoints are geocoded internally. Returns up to 5 itineraries, each with legs, modes, line numbers, and real-time status. Departure time defaults to now; provide an ISO 8601 timestamp with offset to plan ahead. |
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 3 tools
Each tool targets a clearly distinct aspect of transit: geocode for place lookup, stop_departures for real-time departures, and plan_journey for routing. The descriptions reinforce these boundaries, making misselection unlikely.
The naming style is lowercase with underscores, but the grammatical patterns vary: 'geocode' is a single verb, 'plan_journey' is verb_noun, and 'stop_departures' is a noun phrase. This mix is readable but not as consistent as a strict verb_noun convention.
Three tools is at the lower end of the typical well-scoped range, but each tool serves a core transit use case. The set feels slightly sparse for a full public-transport domain, but it is not overly thin or bloated.
The tool surface covers the primary journey-planning workflow: geocoding, departures, and route planning. Minor gaps exist such as no tool for disruptions, fares, or stop metadata, but agents can accomplish the main tasks without dead ends.