Available tools
Available tools
Every tool runs on TomTom Orbis Maps, for both the Remote MCP Server and the local setup.
In clients that support MCP Apps, tool results also appear on an interactive map. See Interactive maps for details.
Search & geocoding
-
tomtom-geocode: Convert street addresses to coordinates (does not support points of interest)
- Documentation: Geocode API documentation
-
tomtom-reverse-geocode: Convert coordinates to addresses
- Documentation: Reverse Geocode API documentation
-
tomtom-fuzzy-search: Typo-tolerant search for addresses, points of interest and geographies
- Documentation: Fuzzy Search API documentation
-
tomtom-poi-search: Find points of interest by category
- Documentation: Points of Interest Search API documentation
-
tomtom-nearby: Find points of interest within a radius of a coordinate
- Documentation: Nearby Search API documentation
-
tomtom-poi-categories: List the point of interest category codes that the search tools accept
- Documentation: POI Categories API documentation
-
tomtom-area-search: Search for places within an area: a circle, a polygon or a bounding box
- Documentation: Geometry Search API documentation
-
tomtom-search-along-route: Find points of interest (restaurants, fuel stations, hotels, etc.) along a route between an origin and a destination
- Documentation: Search Along Route API documentation
-
tomtom-ev-search: Find EV charging stations with their connector types and power levels
- Documentation: Points of Interest Search API documentation
Routing
- tomtom-routing: Calculate a route through an origin, optional stops and a destination, with distance, travel time and traffic delay
- Documentation: Calculate Route API documentation
Traffic
- tomtom-traffic: Look up traffic incidents in an area (accidents, jams, road closures, roadworks, etc.)
- Documentation: Traffic Incident Details API documentation
Maps & data visualization
These tools draw their map in the client through an MCP App, so they need a client that supports MCP Apps.
-
tomtom-dynamic-map: Interactive map with custom markers, routes and polygons
- Documentation: Map Display API documentation
-
tomtom-data-viz: Visualize your own GeoJSON data on an interactive TomTom basemap. Supports markers, heatmaps, clusters, lines, polygon fills and choropleth maps
- Documentation: Map Display API documentation
Getting geometry from a tool response
Tools that return TomTom data accept a response_detail parameter. By default (compact) they return the essential fields and the coordinates of each place, but no route lines, incident locations or search areas, so a response doesn’t use up the model’s context.
tomtom-routing, tomtom-traffic, tomtom-area-search and tomtom-search-along-route also accept geometry.
| Value | Returns |
|---|---|
compact (default) | Essential fields and the coordinates of each place. No route lines, incident locations or search areas. |
geometry | compact, plus a geometry key holding route lines, incident locations and search areas as a GeoJSON FeatureCollection, simplified to at most 1,000 points per feature. |
full | The raw API response. Lossless, but many times larger. |
Use geometry when you need the coordinates themselves, for example to draw the result on your own map. For an Amsterdam to Berlin route, geometry is about 22 KB and full about 210 KB. See the GitHub repository for the format.
Release notes
The release notes on GitHub list the changes in each version, with migration steps for breaking changes.