Skip to main content
Glama

geocode

Geocode addresses, places, or cadastral parcels using IGN's Géoplateforme API and return GeoJSON FeatureCollection results.

Instructions

Géocode une chaîne de caractères (adresse, lieu ou parcelle cadastrale) via l'API Géoplateforme de l'IGN. Retourne une FeatureCollection GeoJSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesChaîne décrivant la localisation à rechercher (adresse, lieu, parcelle). Exemple : '10 rue de la Paix Paris', 'cimetière Vincennes', '75056104AE0003'.
latNoLatitude d'un point pour favoriser les candidats les plus proches.
lonNoLongitude d'un point pour favoriser les candidats les plus proches.
cityNoFiltre par nom de commune (address, poi). Ex : 'Dijon'.
typeNoFiltre par type d'adresse (address uniquement) : 'housenumber', 'street', 'locality', 'municipality'.
indexNoIndex de recherche : 'address' (défaut), 'poi' (lieux/POI), 'parcel' (parcelles cadastrales).
limitNoNombre maximum de résultats (1–50, défaut : 10).
sheetNoFiltre par feuille cadastrale (parcel).
numberNoFiltre par numéro de parcelle (parcel). Ex : '0133'.
depcodeNoFiltre par code département (address, poi). Ex : '75'.
sectionNoFiltre par section cadastrale (parcel). Ex : 'AV'.
categoryNoFiltre par catégorie de POI (poi uniquement, valeurs listées dans getCapabilities). Plusieurs valeurs séparées par des virgules.
citycodeNoFiltre par code INSEE de commune (address, poi). Ex : '75113'.
postcodeNoFiltre par code postal (address, poi). Ex : '75013'.
autocompleteNoActive (1) ou désactive (0) l'autocomplétion (défaut : 1).1
departmentcodeNoFiltre par code département (parcel). Ex : '21'.
municipalitycodeNoFiltre par code commune (parcel). Ex : '231'.
returntruegeometryNoRetourne la vraie géométrie de l'objet (limite le résultat à 20).
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the output format (FeatureCollection GeoJSON) and the data source (IGN Géoplateforme API), but it does not explicitly state that the tool is read-only, nor does it mention any rate limits, geographic scope (likely limited to France), or other behavioral traits beyond the return format.

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?

The description is extremely concise: one sentence for the main action and one for the output. It front-loads the core purpose with no wasted words.

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 the tool has 18 parameters, no output schema, and no annotations, the description is too sparse. It does not explain typical usage, parameter interactions, or the structure of the returned FeatureCollection. It lacks completeness for a complex geocoding tool.

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 description coverage is 100%, so the schema already documents all 18 parameters well. The description adds no additional meaning beyond the schema, only stating it geocodes a string. Baseline 3 is appropriate.

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

Purpose4/5

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

The description clearly states the tool geocodes a string (address, place, or cadastral parcel) via the IGN Géoplateforme API and returns a FeatureCollection GeoJSON. However, it does not explicitly differentiate from sibling tools like geocode_reverse or geocode_capabilities, though the forward geocoding purpose is implicit.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool or when not to use it. It does not mention alternative tools for reverse geocoding or capabilities retrieval, which would be helpful given the sibling tools exist.

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/cvagner/geocodage-mcp'

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