norway-location-transport-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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_addressA | Search official Norwegian addresses (Kartverket) and get coordinates. Use |
| find_addresses_nearA | Find all official addresses within a radius of a coordinate (Kartverket). Each result includes its distance from the point. Good for 'what is at this location?'. |
| validate_addressA | Check whether a free-text address exists in the official register and return its normalized form with coordinates. Uses fuzzy matching, so it also corrects small spelling errors. Returns |
| search_place_namesA | Search official Norwegian place names (Kartverket Sentralt stedsnavnregister). Returns each name's feature type (e.g. Fjell, Innsjø, By), municipality, county, and coordinates. Supports the * wildcard and corrects small spelling errors. |
| find_place_names_nearA | Find the nearest official named features to a coordinate (Kartverket). Each result includes its feature type and distance from the point. |
| get_elevationA | Get the terrain elevation (metres above sea level) at a coordinate from the Norwegian national elevation model (Kartverket DTM). Covers mainland Norway. |
| get_elevation_profileA | Sample the terrain elevation evenly along a path of coordinates (Kartverket DTM) and return the profile plus total distance, ascent, and descent. Useful for hikes and routes. Give the path vertices in order; |
| transform_coordinatesA | Convert a coordinate between reference systems using Kartverket's transformer. Give EPSG codes for source and target. Axis order: x is easting (longitude for geographic systems), y is northing (latitude). Common EPSG codes: 4326 WGS84, 4258 EUREF89 (both lon/lat), 25832 UTM32/EUREF89, 25833 UTM33, 25835 UTM35 (east/north in metres). |
| lookup_admin_unitB | Find which municipality (kommune) and county (fylke) a location falls in, with official codes (Kartverket). Give either a coordinate or a free-text address. |
| lookup_propertyA | Look up cadastral (matrikkel) identifiers for a property via the open address register (Kartverket): municipality number, gårdsnummer (gnr), bruksnummer (bnr), and festenummer. Give a free-text address or a coordinate. Full ownership data requires Kartverket's authenticated Matrikkel API; this returns the open address-linked identifiers. |
| resolve_stop_placeA | Turn a place or address into Entur Stop Place IDs (public transport stops/stations). Use the returned ID with the departure, trip, accessibility, quay, and fare-zone tools. |
| find_stops_nearA | Reverse-geocode a coordinate to the nearest public transport stop places (Entur), each with its distance. Use the returned IDs with the departure and trip tools. |
| plan_tripA | Plan a point-to-point public transport journey in Norway (Entur JourneyPlanner). Give each endpoint either as a Stop Place ID or as coordinates. Optionally set a departure or arrival time, filter transport modes, and set walk speed. Returns trip patterns with legs, modes, durations, and realtime times. |
| get_departuresA | Get the next departures from a stop place (Entur), including realtime delays and cancellations. Each departure shows line, destination, scheduled and expected times, delay, platform, and whether it is cancelled. |
| get_realtime_statusA | Get a realtime health summary. For a stop, pass stop_place_id: it summarizes how many upcoming departures are on time, delayed, or cancelled. For a line, pass line_id: it reports how many vehicles are currently active and their delays. |
| get_stop_accessibilityA | Get accessibility information for a stop place (Entur): per-quay (platform) wheelchair access, and a summary. Note: Entur's free API exposes wheelchair access per quay; deeper equipment detail (elevators, tactile guidance) is only in Entur's authenticated Stop Register API and is not available here. |
| list_quaysB | List all quays (platforms/stopping points) at a stop place (Entur), with their public codes, coordinates, and wheelchair access. |
| get_fare_zonesA | Get the fare (tariff) zone(s) a stop place belongs to (Entur). Fare zones set the ticket price for a journey. |
| find_shared_vehiclesA | Find free-floating shared vehicles (city bikes, e-scooters, car share, mopeds) near a coordinate across all Norwegian operators (Entur Mobility). Each result shows the operator, type, battery, and location. |
| find_docking_stationsA | Find shared-mobility docking stations (e.g. city bike stations) near a coordinate (Entur Mobility), with available vehicle and free-dock counts per station. |
| get_vehicle_positionsA | Get live positions of public transport vehicles (Entur realtime), filtered by operator codespace and/or line. Each vehicle shows its position, bearing, speed, and delay. Codespace examples: ATB (Trondheim), KOL (Stavanger), SKY (Bergen area). Get a line_id from get_departures. |
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 21 tools
Each tool targets a distinct resource and action: address search vs. place name search vs. near-location queries, separate tools for elevation, coordinate transformation, admin lookup, property lookup, and transport-specific tools (stops, departures, trip planning, realtime status, accessibility, quays, fare zones, shared mobility, vehicle positions). No two tools have overlapping purposes that would cause misselection.
The naming follows a consistent verb_noun pattern throughout (e.g., search_address, find_place_names_near, get_elevation, lookup_admin_unit, plan_trip, get_departures). The 'find_*_near' variant is uniformly applied to both addresses and place names, and all tools use snake_case with descriptive verbs. Minor variation like 'list_quays' is still within a clear convention.
21 tools is on the higher end of the typical range, but the server covers a broad domain combining location data (addresses, place names, elevation, coordinates) and transport (stops, journeys, realtime, mobility). Each tool serves a distinct function, so the count feels justified for the scope, though it is slightly heavier than the ideal 3-15 tool range.
The tool surface is remarkably complete for Norwegian location and transport services. It covers address and place name search (with near-location variants), validation, elevation (point and profile), coordinate transformation, administrative unit lookup, property lookup, stop place resolution and reverse geocoding, journey planning, departures, realtime status, accessibility, quay listing, fare zones, and both free-floating and docking shared mobility. No obvious gaps in core workflows were identified.