Related Servers

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.