Loading ToolBench
MCP server integrating TomTom APIs for maps, routing, search, traffic, and data visualization
Strong tool coverage (20 tools) with consistent naming patterns (verb_noun: get_, search_, find_) and comprehensive descriptions (100-300 chars typical). All tools have descriptions and most parameters are typed. However, input schemas are not visible in the provided source excerpt, preventing full schema validation. Tool descriptions are well-structured with WHEN-to-use guidance (e.g., tomtom-routing vs tomtom-waypoint-routing distinction is clear). Error handling and output schemas are not documented in the visible code. Security is sound (no API keys in params). Composition is excellent, tools are single-responsibility and chainable (e.g., poi-categories → poi-search). Baseline: 194 chars avg description length; these tools average ~180-220 chars, within range.
Find all POIs within a strict geographic boundary — polygon, bounding box, or circle. Use this when the search must be confined to a specific region (e.g. 'restaurants inside Westminster', 'hotels within this polygon'). Unlike tomtom-nearby (radius from a point) or tomtom-poi-search (location bias), this tool guarantees results are inside the defined geometry.
Visualize custom GeoJSON data on an interactive TomTom basemap. Intended for large datasets, heatmaps, cluster maps, choropleth maps, or GeoJSON data (from a URL or inline) rendered on a map. Supports markers, heatmaps, clusters, lines, polygon fills, and choropleth maps. Provide data via HTTPS URL or inline GeoJSON. Multiple layers can be overlaid in a single call. Point features are automatically enriched with TomTom address data when clicked (reverse geocode). Placing a few specific markers, routes, or polygons is handled by tomtom-dynamic-map; route calculations (directions, travel time) are handled by tomtom-routing.
Render a custom map image with markers, drawn lines, polygons, and area overlays — with interactive map UI. Intended for map visualization: showing locations on a map, highlighting areas, or combining multiple visual elements in one view. Not intended for route calculations (tomtom-routing), traffic incidents (tomtom-traffic), or large-dataset visualization like heatmaps/clusters/choropleth (tomtom-data-viz). The optional routePlans parameter can calculate and draw routes on the map; it is meant for routes combined with other map elements (markers, polygons) in a single image.
Input schemas not visible in source code. Cannot verify parameter types, descriptions, or constraints. Provided tool list shows only one tool (tomtom-get-viz-data) with a visible schema fragment. For 19 of 20 tools, schema completeness cannot be assessed.
Output schemas not documented in visible source. Tool descriptions mention what is returned (e.g., 'turn-by-turn directions, distance, travel time, and an interactive map' for tomtom-routing) but formal output schema definitions are absent. LLMs cannot plan downstream tool calls without knowing response structure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2026-07-28+ | v2 |
Plan long-distance electric vehicle routes with automatic charging stop optimization. Calculates optimal charging stops based on battery state, vehicle model, and charging connector compatibility. Uses TomTom Maps SDK.
Find EV charging stations with real-time availability, connector types, and power levels. Uses TomTom Maps SDK for enriched results with charger status (available/occupied/out-of-service).
Typo-tolerant search for addresses, points of interest, and geographies with interactive map UI
Convert street addresses to coordinates with interactive map UI
Internal tool for apps to retrieve the TomTom API key
Internal tool for apps to retrieve client configuration such as the attribution user-agent
Internal tool for apps to retrieve cached visualization data by viz_id
Find places close to a specific point. Best for 'what's around here?' queries when you have exact coordinates (lat/lon). Returns results sorted by distance. Use tomtom-area-search instead when the search area is a polygon or bounding box rather than a simple radius.
Look up POI category codes from natural language. The poiCategories parameter of the search tools accepts only codes returned by this tool. Category codes are UPPER_SNAKE_CASE text strings (e.g. 'ITALIAN_RESTAURANT', 'PARKING_GARAGE'), not numeric IDs. Workflow: (1) extract the user's intent as keywords (e.g. 'italian restaurants in Amsterdam' → filters: ['italian restaurant']); (2) call this tool with those keywords in the filters parameter; (3) pass the returned category codes in the poiCategories parameter of search tools (fuzzy-search, poi-search, nearby, area-search). Guessed or hardcoded category codes are unreliable; this tool is the source of valid codes.
Search for a specific business or POI by name, or browse an entire POI category. Best for finding a known place (e.g. 'Starbucks') or listing all businesses of a type (e.g. the 'ITALIAN_RESTAURANT' category code from tomtom-poi-categories). Supports optional location bias but does not constrain results to a strict geographic boundary — tomtom-area-search does that.
Determine the area reachable within a specified time or driving distance with interactive map UI
Convert coordinates to addresses with interactive map UI
Calculate optimal routes through an ordered list of locations [origin, ...stops, destination]. The primary tool for directions, routes, travel time, or distance between places — whether a simple A-to-B or a multi-stop itinerary (e.g. 'route from Amsterdam to Berlin', 'drive from A to B via C and D'). Returns turn-by-turn directions, distance, travel time, and an interactive map. Visualizing multiple routes or combining routes with markers/polygons on a single map image is handled by tomtom-dynamic-map.
Find points of interest (restaurants, gas stations, hotels, etc.) along a calculated route with interactive map UI
Generate custom map images from TomTom Maps with specified center coordinates, zoom levels, and style options
Find and display traffic incidents in an area on an interactive map. The primary tool for questions about traffic, accidents, road closures, congestion, or dangerous road conditions. Incidents are rendered as styled icons on the map and can be clicked for details (severity, description, delay, road name). Already provides a complete interactive traffic visualization; plotting incidents as markers with tomtom-dynamic-map is not needed.
Plan multi-stop routes through 3 or more waypoints. Use when the user needs to visit multiple locations in sequence (e.g. 'route from A to B via C and D'). Returns optimized turn-by-turn directions, total distance, and travel time. For simple A-to-B routes, use tomtom-routing instead.
Error handling and recovery guidance not visible. No evidence of error classification (retryable vs user-fixable vs fatal), actionable error messages, or recovery suggestions in tool descriptions or visible code.
Pagination and result limits not documented. Tools like tomtom-poi-search, tomtom-fuzzy-search, and tomtom-area-search may return large result sets, but no limit, offset, or cursor parameters are visible. Risk of context window exhaustion.
Parameter descriptions missing for most tools. Only tomtom-get-viz-data shows a parameter description ('Unique visualization ID from the tool response _meta'). Other 19 tools have no visible parameter documentation, violating the 100% baseline for A+ tools.