Skip to main content
Glama
mapbox

Mapbox MCP Server

Official

Reverse Geocode Tool

reverse_geocode_tool
Read-onlyIdempotent

Convert geographic coordinates into a human-readable address or place name. Use when you need an address from latitude and longitude.

Instructions

Convert geographic coordinates (longitude, latitude) into a human-readable address or place name. Use only when you need an address/place name alone. If you also need nearby places, neighborhood context, or travel-time reachability, use ground_location_tool instead — it already includes reverse geocoding plus POI search and isochrone in one call. This tool cannot reverse geocode businesses, landmarks, or POIs. Supports JSON and text output formats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results (1-5). Use 1 for best results. If you need more than 1 result, you must specify exactly one type in the types parameter.
typesNoArray of feature types to filter results
formatNoOutput format: "json_string" returns raw GeoJSON data as a JSON string that can be parsed; "formatted_text" returns human-readable text with place names, addresses, and coordinates. Both return as text content but json_string contains parseable JSON data while formatted_text is for display.formatted_text
countryNoArray of ISO 3166 alpha 2 country codes to limit results
languageNoIETF language tag for the response (e.g., "en", "es", "fr", "de", "ja")
latitudeYesLatitude coordinate to reverse geocode
longitudeYesLongitude coordinate to reverse geocode
permanentNoWhether results can be stored permanently
worldviewNoReturns features from a specific regional perspectiveus

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
featuresYes
attributionYes
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, etc. Description adds that it supports JSON and text output formats, clarifies it cannot reverse geocode businesses/landmarks, and does not contradict annotations.

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

Conciseness5/5

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

Very concise: two sentences plus a hint. Front-loaded with purpose and usage guidance. Every sentence adds value.

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

Completeness5/5

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

Given 9 parameters, full schema coverage, and an output schema, the description is complete. It covers purpose, usage guidelines, limitations, and output formats. No gaps.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description does not add significant meaning beyond what is already in the schema parameter descriptions; it only mentions output formats briefly.

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

Purpose5/5

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

Clearly states the tool converts geographic coordinates into a human-readable address or place name. Distinguishes from ground_location_tool by specifying that this tool is only for address/place name, not for nearby places or travel-time reachability.

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

Usage Guidelines5/5

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

Explicitly says 'Use only when you need an address/place name alone' and contrasts with ground_location_tool which includes reverse geocoding plus POI search and isochrone. Also states limitation: cannot reverse geocode businesses, landmarks, or POIs.

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

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/mapbox/mcp-server'

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