TomTom MCP integration for AI agents.
Connect AI agents to TomTom through 5 structured actions, including fuzzy search, autocomplete, and geocode. Review authentication, inputs, workflows, and sa…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the TomTom integration exposes
The TomTom Agent App exposes 5 provider-backed actions for location and developer tools work. Its current contract lets an authorized agent search addresses or places with the tomtom search api fuzzy search endpoint, return autocomplete suggestions from the tomtom search api, and convert an address into geographic search results with the tomtom geocoding api. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected TomTom account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real TomTom capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
fuzzy_searchREADSearch addresses or places with the TomTom Search API fuzzy search endpoint.
INPUTS: query / limit / offset / countrySet / lat
autocompleteREVIEWReturn autocomplete suggestions from the TomTom Search API.
INPUTS: query / language / limit / lat / lon
geocodeREVIEWConvert an address into geographic search results with the TomTom Geocoding API.
INPUTS: query / limit / offset / lat / lon
nearby_searchREADSearch for nearby places of interest around a coordinate with TomTom.
INPUTS: lat / lon / radius / limit / offset
reverse_geocodeREVIEWConvert a coordinate into human-readable address candidates with the TomTom Reverse Geocoding API.
INPUTS: lat / lon / radius / entityType / language
INPUT CONTRACTS
Know what the action needs before it runs.
fuzzy_search
queryREQUIRED- The free-form text query sent to TomTom.
limitOPTIONAL- The maximum number of results to return.
offsetOPTIONAL- The zero-based result offset used for pagination.
countrySetOPTIONAL- The country filters applied to the TomTom request.
latOPTIONAL- The latitude in decimal degrees.
autocomplete
queryREQUIRED- The partial text query used for autocomplete suggestions.
languageREQUIRED- The IETF language tag for results.
limitOPTIONAL- The maximum number of autocomplete results to return.
latOPTIONAL- The latitude in decimal degrees.
lonOPTIONAL- The longitude in decimal degrees.
geocode
queryREQUIRED- The address or place query to geocode.
limitOPTIONAL- The maximum number of results to return.
offsetOPTIONAL- The zero-based result offset used for pagination.
latOPTIONAL- The latitude in decimal degrees.
lonOPTIONAL- The longitude in decimal degrees.
nearby_search
latREQUIRED- The latitude in decimal degrees.
lonREQUIRED- The longitude in decimal degrees.
radiusOPTIONAL- The search radius in meters.
limitOPTIONAL- The maximum number of results to return.
offsetOPTIONAL- The zero-based result offset used for pagination.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Fuzzy Search
Search addresses or places with the TomTom Search API fuzzy search endpoint. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
fuzzy_searchVerify with Nearby Search
Search for nearby places of interest around a coordinate with TomTom. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
nearby_searchSAFETY BOUNDARY
Operate TomTom with explicit limits
- Authorize TomTom with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned TomTom data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in TomTom rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the TomTom task completed successfully.
CONNECTION MODEL
API key
TomTom API key sent as the key query parameter. Create and manage keys at https://developer.tomtom.com/how-to-get-tomtom-api-key.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 3
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by TomTom.