Skip to main content
Glama
tomtom-international

TomTom MCP Server

Official

tomtom-geocode

Convert addresses to precise geographic coordinates using detailed query inputs, language preferences, and country filters. Ideal for integrating accurate location data into applications and workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressRangesNoInclude address ranges in the response
btmRightNoBottom-right coordinates of bounding box (format: 'lat,lon'). Must be used with topLeft
countrySetNoLimit results to specific countries using ISO codes. Examples: 'US', 'FR,GB', 'CA,US'
entityTypeSetNoFilter 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
extendedPostalCodesForNoInclude extended postal codes for specific index types. Examples: 'PAD', 'PAD,Addr', 'POI'
geometriesNoInclude geometries information in the response
languageNoPreferred language for results using IETF language tags. Examples: 'en-US', 'fr-FR', 'de-DE', 'es-ES'
latNoCenter latitude for location bias
limitNoMaximum number of results to return (1-100). Default: 5
lonNoCenter longitude for location bias
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).
queryYesFull address to convert to coordinates. Include as much detail as possible (street, city, country) for accurate results. Examples: '1600 Pennsylvania Ave, Washington DC', 'Eiffel Tower, Paris, France'
radiusNoSearch radius in meters when lat/lon provided
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
viewNoGeopolitical view for disputed territories. Options: 'Unified', 'AR', 'IL', 'IN', 'MA', 'PK', 'RU', 'TR', 'CN'

Implementation Reference

  • Factory function creating the async handler for the 'tomtom-geocode' tool. It extracts the query, calls the geocodeAddress service with optional parameters, logs the process, and returns JSON-formatted results or error.
    export function createGeocodeHandler() {
      return async (params: any) => {
        logger.info(`🏠 Geocoding: "${params.query}"`);
        try {
          const { query, ...options } = params;
          const result = await geocodeAddress(
            query,
            Object.keys(options).length > 0 ? options : undefined
          );
          logger.info(`✅ Geocoding successful for: "${query}"`);
          return { content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }] };
        } catch (error: any) {
          logger.error(`❌ Geocoding failed: ${error.message}`);
          return {
            content: [{ type: "text" as const, text: JSON.stringify({ error: error.message }) }],
            isError: true,
          };
        }
      };
    }
  • Zod schema defining the input parameters for the 'tomtom-geocode' tool, including query and various search options.
    export const tomtomGeocodeSearchSchema = {
      query: z
        .string()
        .describe(
          "Full address to convert to coordinates. Include as much detail as possible (street, city, country) for accurate results. Examples: '1600 Pennsylvania Ave, Washington DC', 'Eiffel Tower, Paris, France'"
        ),
      ...baseSearchParams,
      ...locationBiasParams,
      ...boundingBoxParams,
      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`
        ),
    };
  • Registration of the 'tomtom-geocode' tool on the MCP server, specifying title, description, input schema, and handler function.
    server.registerTool(
      "tomtom-geocode",
      {
        title: "TomTom Geocode",
        description: "Convert street addresses to coordinates (does not support points of interest)",
        inputSchema: schemas.tomtomGeocodeSearchSchema,
      },
      createGeocodeHandler()
    );
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