Skip to main content
Glama
tomtom-international

TomTom MCP Server

Official

tomtom-poi-search

Search for points of interest (POIs) by category, location, or specific filters like EV charging stations, fuel types, or brands. Retrieve detailed results with language, mapcodes, and geometry data for precise geolocation needs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressRangesNoInclude address ranges in the response
brandSetNoFilter by brand names. Examples: 'Starbucks,Peet\'s', 'Marriott,Hilton'. Use quotes for brands with commas.
btmRightNoBottom-right coordinates of bounding box (format: 'lat,lon'). Must be used with topLeft
categorySetNoFilter by POI categories. Common IDs: '7315' (restaurants), '7309' (gas), '7311' (hotels), '9663' (EV charging).
chargingAvailabilityNoInclude charging availability information for EV stations
connectorSetNoEV connector types: 'IEC62196Type2CableAttached', 'Chademo', 'TeslaConnector'
countrySetNoLimit results to specific countries using ISO codes. Examples: 'US', 'FR,GB', 'CA,US'
entityTypeSetNoFilter results by entity types
extNoExtended parameters for the search
extendedPostalCodesForNoInclude extended postal codes for specific index types. Examples: 'PAD', 'PAD,Addr', 'POI'
fuelAvailabilityNoInclude fuel availability information for gas stations
fuelSetNoFuel types: 'Petrol', 'Diesel', 'LPG', 'Hydrogen', 'E85'
geometriesNoInclude geometries information in the response
languageNoPreferred language for results using IETF language tags. Examples: 'en-US', 'fr-FR', 'de-DE', 'es-ES'
latNoLatitude for location context. STRONGLY recommended for relevant local results.
limitNoMaximum number of results to return (1-100). Default: 5
lonNoLongitude for location context. Must be used with lat parameter.
mapcodesNoInclude mapcode information in the response. Mapcodes represent specific locations within a few meters and are designed to be short, easy to recognize and communicate. Options: Local, International, Alternative. Examples: 'Local' (local mapcode only), 'Local,Alternative' (multiple types). Accepts array of string(s).
maxFuzzyLevelNoMaximum fuzzy matching level (1-4)
maxPowerKWNoMaximum charging power in kW for EV stations
minFuzzyLevelNoMinimum fuzzy matching level (1-4)
minPowerKWNoMinimum charging power in kW for EV stations
ofsNoOffset for pagination of results
openingHoursNoList of opening hours for a POI (Points of Interest).Value: `nextSevenDays` Mode shows the opening hours for next week, starting with the current day in the local time of the POI. Usage example: openingHours=nextSevenDays
parkingAvailabilityNoInclude parking availability information
queryYesSpecific POI category search. Best for finding types of businesses: 'restaurants', 'gas stations', 'hotels', 'parking', 'ATMs', 'hospitals'
radiusNoSearch radius in meters. Essential for focused local results. Examples: 1000 (walking), 5000 (driving), 20000 (wide area).
relatedPoisNoInclude related points of interest
roadUseNoInclude road usage information
sortNoSort options for results
timeZoneNoUsed to indicate the mode in which the timeZone object should be returned. Values: iana Mode shows the IANA ID which allows the user to determine the current time zone for the POI. Usage examples: timeZone=iana
topLeftNoTop-left coordinates of bounding box (format: 'lat,lon'). Must be used with btmRight
typeaheadNoAutocomplete mode for partial queries. Use for search interfaces.
vehicleTypeSetNoA comma-separated list of vehicle types that could be used to restrict the result to the Points Of Interest of specific vehicles. If vehicleTypeSet is specified, the query can remain empty. Only POIs with a proper vehicle type will be returned. Value: A comma-separated list of vehicle type identifiers (in any order). When multiple vehicles types are provided, only POIs that belong to (at least) one of the vehicle types from the provided list will be returned. Available vehicle types: Car , Truck
viewNoGeopolitical view for disputed territories. Options: 'Unified', 'AR', 'IL', 'IN', 'MA', 'PK', 'RU', 'TR', 'CN'

Implementation Reference

  • MCP tool handler factory for 'tomtom-poi-search'. Handles input parameters, calls the POI search service, logs activity, formats response as JSON text, and manages errors.
    export function createPoiSearchHandler() {
      return async (params: any) => {
        logger.info(`🏪 POI search: "${params.query}"`);
        try {
          const result = await poiSearch(params.query, params);
          logger.info(`✅ POI search completed`);
          return { content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }] };
        } catch (error: any) {
          logger.error(`❌ POI search failed: ${error.message}`);
          return {
            content: [{ type: "text" as const, text: JSON.stringify({ error: error.message }) }],
            isError: true,
          };
        }
      };
    }
  • Zod schema defining input parameters for the tomtom-poi-search tool, including query, location bias, filters, radius, and POI-specific options.
    export const tomtomPOISearchSchema = {
      query: z
        .string()
        .describe(
          "Name of the POI to search for. If the intended query is a POI category like 'restaurant', provide an empty string for this param and use the category filter parameter to apply the desired category filter."
        ),
      ...baseSearchParams,
      ...locationBiasParams,
      ...boundingBoxParams,
      ...poiFilterParams,
      radius: z
        .number()
        .optional()
        .describe(
          "Search radius in meters. Essential for focused local results. Examples: 1000 (walking), 5000 (driving), 20000 (wide area)."
        ),
      lat: z
        .number()
        .optional()
        .describe("Latitude for location context. STRONGLY recommended for relevant local results."),
      lon: z
        .number()
        .optional()
        .describe("Longitude for location context. Must be used with lat parameter."),
      typeahead: z
        .boolean()
        .optional()
        .describe("Autocomplete mode for partial queries. Use for search interfaces."),
      entityTypeSet: z.string().optional()
      .describe(`Filter results by geographic entity types. Valid values: PostalCodeArea,
          CountryTertiarySubdivision, CountrySecondarySubdivision, MunicipalitySubdivision,
          MunicipalitySecondarySubdivision, Country, CountrySubdivision, Neighbourhood, Municipality.
          Note: This parameter is for geographic entities only, not POIs.
          For POI filtering, use categorySet instead`
        ),
      chargingAvailability: z
        .boolean()
        .optional()
        .describe("Include charging availability information for EV stations"),
      parkingAvailability: z.boolean().optional().describe("Include parking availability information"),
      fuelAvailability: z
        .boolean()
        .optional()
        .describe("Include fuel availability information for gas stations"),
      minFuzzyLevel: z.number().optional().describe("Minimum fuzzy matching level (1-4)"),
      maxFuzzyLevel: z.number().optional().describe("Maximum fuzzy matching level (1-4)"),
      ofs: z.number().optional().describe("Offset for pagination of results"),
      relatedPois: z.string().optional().describe("Include related points of interest"),
      ext: z.string().optional().describe("Extended parameters for the search"),
    };
  • Registers the 'tomtom-poi-search' tool on the MCP server with title, description, input schema, and handler factory.
    server.registerTool(
      "tomtom-poi-search",
      {
        title: "TomTom POI Search",
        description: "Find specific business categories",
        inputSchema: schemas.tomtomPOISearchSchema,
      },
      createPoiSearchHandler()
    );
  • Core POI search function that constructs API parameters and calls the TomTom POI Search API endpoint.
    export async function poiSearch(
      query: string,
      options?: ExtendedSearchOptions
    ): Promise<SearchResult> {
      const params = buildSearchParams(options, {
        limit: 10,
        language: "en-US",
      });
    
      return makeApiCall(
        `/search/${API_VERSION.SEARCH}/poiSearch/${encodeURIComponent(query)}.json`,
        params,
        `POI searching for: "${query}"`
      );
    }
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tomtom-international/tomtom-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server