Skip to main content
Glama

mapbox_geocode_forward

Convert an address or place name to geographic coordinates with Mapbox. Specify query, country, language, limit, proximity, or type filters for precise geocoding results.

Instructions

Convert an address or place name to coordinates using Mapbox.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
access_tokenYesMapbox access token from account.mapbox.com
queryYesAddress or place name to geocode
countryNoLimit results to a country (ISO 3166 alpha-2, e.g. US)
languageNoLanguage for results (e.g. en, fr)
limitNoMax results (1-10, default: 5)
proximityNoBias results near coordinates (lng,lat)
typesNoFilter by feature types (e.g. address,place,poi)
Behavior2/5

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

No annotations provided; description fails to disclose behavioral traits such as authentication requirements, rate limits, or error handling. Only the purpose is stated.

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

Conciseness3/5

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

The description is extremely concise (one sentence) and front-loaded, but lacks important details necessary for an AI agent to use it effectively.

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

Completeness2/5

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

Given 7 parameters and no output schema, the description is incomplete; it does not explain coordinate system, batch capabilities, or error handling, leaving significant 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% with parameter descriptions; the tool description adds no additional semantic meaning beyond the schema, meeting the baseline.

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?

The description clearly states the tool converts addresses or place names to coordinates, distinguishing it from the sibling mapbox_geocode_reverse which does the opposite.

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

Usage Guidelines3/5

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

The description implies use for forward geocoding but provides no explicit guidance on when to use this tool versus alternatives like mapbox_geocode_reverse or other mapbox tools.

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/malamutemayhem/unclick'

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