Skip to main content

Overview

Search for a place or address and convert it into coordinates. Use this tool when the user provides:
  • a place name
  • a landmark
  • a business
  • a street address
  • another location description
Do not use it when the user already provides coordinates in longitude,latitude format.

Structured input

The search is structured. Parse the user’s location into the fields that can be determined:
  • name — place, landmark, or business name
  • housenumber — house or building number
  • street — street name
  • postcode — postal or ZIP code
  • city — city or locality
  • country — country
Only provide fields that are known from the user’s request. Do not invent or guess missing address components. For example:
When the user’s context provides a country or city, include it to disambiguate common, abbreviated, or misspelled place names.

Limit and filters

limit is optional and defaults to 1. The maximum value is 10. Use a larger limit when the location is ambiguous or the user asks for alternatives. filters can optionally restrict the search. For example:

Output

Results are ordered by relevance. By default, the best matching result is returned. If multiple results are requested, choose the result that best matches the user’s intended location. The coordinates value is in longitude,latitude format and can be passed directly to route, table, or optimize. When using geocode as part of a routing workflow, verify that the selected result matches the user’s intended place before passing its coordinates to the next tool. If no result matches, the tool returns an error so the assistant can refine the search.

Example

Prompt for an MCP-capable agent, e.g. Claude or Codex