Tomtom

@tomtom find all EV charging stations within 5km of downtown Seattle and show me which ones have CCS fast chargers available right now

Found 12 EV charging stations within 5km of downtown Seattle. Of these, 4 have CCS fast chargers with real-time availability: ChargePoint Station (Pike St) has 2/4 connectors available, Electrify America (Convention Center) has 3/6 available, EVgo (Capitol Hill) has 1/2 available, and Shell Recharge (Westlake) has 4/4 available. The remaining 8 stations either lack CCS connectors or don't report live availability data. Closest available CCS charger is 0.8km from your search center.

This example combines Category Search with EV Charging Stations Availability to demonstrate location-based filtering plus live data retrieval. Real availability requires valid connector set IDs and POI IDs from the initial search. TomTom's coverage varies by region—some charging networks don't share real-time data.

@tomtom calculate the fastest route from San Francisco to Los Angeles with a stop in San Luis Obispo, accounting for current traffic conditions

Route calculated: SF to LA via San Luis Obispo, total distance 383 miles, estimated time 6 hours 12 minutes with current traffic. Depart SF southbound on US-101, waypoint stop in San Luis Obispo after 231 miles (3h 45m), then continue 152 miles to LA (2h 27m). Traffic delay adds approximately 28 minutes compared to free-flow conditions—heaviest congestion detected near San Jose (northbound) and approaching LA metro area. Route avoids I-5 due to construction delays reported near Coalinga.

Calculate Route demonstrates multi-waypoint planning with live traffic integration. The response includes distance, time, and traffic-aware routing decisions. Note that traffic data accuracy depends on TomTom's real-time feed coverage—rural segments may show estimated rather than observed conditions.

@tomtom search for 'coffee shop' near the Eiffel Tower and summarize which ones have the highest ratings based on POI data

Fuzzy Search returned 18 coffee shops within 1km of the Eiffel Tower. TomTom POI data doesn't include user ratings, but I can identify prominent chains and independent cafés: Café de l'Homme (Trocadéro, 0.3km), Carette (Place du Trocadéro, 0.4km), Starbucks (Avenue de la Bourdonnais, 0.5km), and several local establishments along Rue Saint-Dominique. For ratings, you'd need to cross-reference these results with a reviews platform like Google Places or Yelp, as TomTom focuses on location and category data rather than sentiment scoring.

Fuzzy Search excels at flexible, typo-tolerant location queries and returns structured POI data (name, address, coordinates, category). However, TomTom's dataset doesn't include reviews or ratings—this example shows how to pair the MCP's output with external context or other data sources for richer insights.

When TomTom beats Google Maps for multi-stop dispatch

A 6-person HVAC company runs 3 trucks doing 8-12 service calls per day. The dispatcher uses Switchy to calculate routes with waypoints and live traffic through TomTom's Calculate Route tool, then shares the optimized sequence in Slack. This works because TomTom's routing API handles up to 150 waypoints per request and returns turn-by-turn instructions the drivers can follow without switching apps. The trade-off: if your team needs real-time driver location tracking or two-way dispatch updates, TomTom is read-only—you'll need a fleet management platform on top. But for morning route planning where the dispatcher owns the sequence and drivers execute it, TomTom gives you enterprise routing without enterprise pricing. If your daily stop count is under 20 per vehicle and routes change less than twice per shift, this is the call.

Why TomTom's Category Search fits retail pickup workflows

A 10-person DTC brand launches buy-online-pick-up-in-store and needs a store locator on their site. The dev team uses Switchy to prototype the Category Search and Fuzzy Search tools, testing queries like 'coffee shops near 10014' to understand response shape before writing production code. TomTom returns POI data with opening hours, phone numbers, and distance—enough to build a working locator in a sprint. The threshold: if you need indoor maps, real-time inventory at each location, or custom POI categories your brand defines, TomTom won't cover it. But for finding your own retail locations or third-party pickup partners within a radius, the API is fast and the category taxonomy is broad. If your store count is under 500 and you're not doing sub-meter accuracy, TomTom gets you live in two weeks.

When TomTom's charging data supports product discovery

A 4-person startup is building a trip planner for EV drivers and needs to validate whether live charging station availability is feasible. The PM uses Switchy to call TomTom's EV Charging Stations Availability tool during user interviews, showing real-time connector status for stations along a test route. This works for early-stage research because TomTom's data covers major networks in North America and Europe, and the API returns availability within 2 seconds. The catch: you need the connectorSetID and poiID upfront, which means you're chaining a search call first—adds latency if you're doing this on every map pan. If your MVP is route-based (user enters start and end, you show charging stops), TomTom fits. If you're building a live map where users browse stations freely, expect 4-6 second load times. For a 3-month prototype budget, this is the dataset to start with.