trafikverket-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRAFIKVERKET_API_KEY | Yes | Trafikverket API key (free from https://api.trafikinfo.trafikverket.se/) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weather_stationA | Get current weather data for a specific Swedish weather station by name. Returns temperature, humidity, wind, precipitation, and road conditions. Use this to check current road weather conditions in Sweden. |
| list_weather_stationsA | List available Swedish weather stations with optional name filtering. Use this to discover station names before querying specific weather data. Search uses case-insensitive substring matching (e.g., 'Timrå', 'Fjärryta', 'Uppsala', '222', 'Lidingöbron'). |
| get_weather_stations_near_locationA | Find weather measurement stations near a specific geographic location. Returns stations within the specified radius, sorted by distance. Coordinates must be in WGS84 format (latitude, longitude). Example: weather stations near Skellefteå (latitude: 64.75, longitude: 20.95) |
| get_camerasA | Get information about traffic cameras in Sweden with photo URLs. Returns camera details including photo URLs, location, direction, county, and GPS coordinates. Use the photo URLs to fetch current camera images. Can be filtered by camera name pattern or by Swedish county number. |
| get_cameras_near_locationA | Find traffic cameras near a specific geographic location. Returns cameras within the specified radius, sorted by distance. Coordinates must be in WGS84 format (latitude, longitude). Example: cameras near Skellefteå (latitude: 64.75, longitude: 20.95) |
| get_weather_observationsB | Get historical weather observations for a specific measurement point. Returns time-series data of past weather conditions. Useful for analyzing weather trends. |
| get_traffic_situationsA | Get current traffic situations including accidents, roadwork, closures, and incidents in Sweden. Returns active traffic disturbances with severity levels, locations, and time information. Can be filtered by road number or county. |
| get_traffic_flowB | Get real-time traffic flow data including vehicle counts and average speeds at measurement points. Returns current traffic density and speed information from monitoring sites across Sweden. |
| get_road_conditionsB | Get current road condition status including ice, snow, and water on road surfaces. Returns location-specific information about road surface conditions and temperatures. Can be filtered by road number. |
| get_camera_imageA | Fetch the actual image from a traffic camera. Takes a photo URL (obtained from get_cameras tool) and returns the image as base64-encoded data. Use this to retrieve the current traffic camera photo for viewing. |
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 target distinct resources and actions, such as cameras, weather stations, traffic situations, traffic flow, and road conditions. However, get_weather_station, list_weather_stations, get_weather_stations_near_location, and get_weather_observations have some overlap in weather-station-related retrieval, and get_road_conditions partially overlaps with weather station road condition data. Descriptions help clarify, but an agent could still hesitate between current station weather and historical observations.
The set is almost entirely consistent snake_case with a get_ prefix (e.g., get_weather_station, get_cameras, get_traffic_flow), which is predictable. The one deviation is list_weather_stations, which uses a different verb but is still conventional and readable. Overall the naming is coherent with a minor stylistic variation.
Ten tools is a well-scoped size for a domain-specific Swedish traffic and weather data server. Each tool covers a distinct data type or access pattern, and there is no evident bloat or missing essential operation within the count itself.
The surface covers cameras (list, near-location, image), weather stations (list, specific, near-location, historical observations), traffic situations, traffic flow, and road conditions. This is broad and lifecycle-appropriate for the apparent domain. Minor gaps may exist, such as no direct near-location query for traffic situations, but agents can likely work around that with existing filters.