Skip to main content
Glama

Géocoder une adresse

geocode_address
Read-only

Convert a French address or place name into geographic coordinates using the IGN Geoplateforme geocoding service. Returns matching locations with coordinates, postal code, city, and relevance score.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "geocode_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesAddress or place name to search for in France. Examples: "20 avenue de Segur, Paris", "Mairie de Bordeaux", "33000"
limitNoMaximum number of results to return (default: 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / q / minLength
      Removed value: -3
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "count": {
      -      "description": "Number of results found",
      -      "type": "number"
      -    },
      -    "results": {
      -      "description": "Array of geocoding results with coordinates",
      -      "items": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "city": {
      -            "description": "City name",
      -            "type": "string"
      -          },
      -          "citycode": {
      -            "description": "INSEE city code",
      -            "type": "string"
      -          },
      -          "context": {
      -            "description": "Geographic context (department, region)",
      -            "type": "string"
      -          },
      -          "label": {
      -            "description": "Full formatted address",
      -            "type": "string"
      -          },
      -          "latitude": {
      -            "description": "Latitude coordinate",
      -            "type": "number"
      -          },
      -          "longitude": {
      -            "description": "Longitude coordinate",
      -            "type": "number"
      -          },
      -          "name": {
      -            "description": "Name of the location",
      -            "type": "string"
      -          },
      -          "postcode": {
      -            "description": "Postal code",
      -            "type": "string"
      -          },
      -          "score": {
      -            "description": "Relevance score (0-1)",
      -            "type": "number"
      -          },
      -          "type": {
      -            "description": "Result type (e.g., housenumber, street, municipality)",
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "label",
      -          "score",
      -          "type",
      -          "name",
      -          "postcode",
      -          "city",
      -          "citycode",
      -          "context",
      -          "longitude",
      -          "latitude"
      -        ],
      -        "type": "object"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "required": [
      -    "count",
      -    "results"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. Changed8 schema fields changed
    • changedOutput schema / properties / count / description
      Previous value: -"Number of results returned"New value: +"Number of results found"
    • changedOutput schema / properties / results / description
      Previous value: -"Geocoding results ordered by relevance"New value: +"Array of geocoding results with coordinates"
    • changedOutput schema / properties / results / items / properties / context / description
      Previous value: -"Administrative hierarchy (department, region)"New value: +"Geographic context (department, region)"
    • changedOutput schema / properties / results / items / properties / latitude / description
      Previous value: -"Latitude (WGS84)"New value: +"Latitude coordinate"
    • changedOutput schema / properties / results / items / properties / longitude / description
      Previous value: -"Longitude (WGS84)"New value: +"Longitude coordinate"
    • changedOutput schema / properties / results / items / properties / name / description
      Previous value: -"Street name or place name"New value: +"Name of the location"
    • changedOutput schema / properties / results / items / properties / score / description
      Previous value: -"Relevance score between 0 and 1"New value: +"Relevance score (0-1)"
    • changedOutput schema / properties / results / items / properties / type / description
      Previous value: -"Result type: housenumber, street, locality, municipality"New value: +"Result type (e.g., housenumber, street, municipality)"
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by naming the external service used and enumerating the return payload (coordinates, postal code, city, relevance score), which matters since no output schema exists. It omits any note on rate limits, error/empty-result behavior, or result ranking beyond the relevance score.

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?

Two sentences, no filler: the operation and service come first, the return shape second. Every clause carries information an agent can act on.

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

Completeness4/5

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

For a simple two-parameter read-only lookup with a fully documented schema and coverage from annotations, this is nearly sufficient: scope, service, and return fields are all stated. The remaining gap is behavior on ambiguous or zero-result queries, which an agent would still have to discover by calling it.

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%, and the schema itself gives the query examples and the limit bounds with a default, so the description need not repeat them. It adds only the France-only constraint on 'q', which is modest value over an already complete schema — baseline 3.

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 opens with a specific verb and resource ('Convert a French address or place name into geographic coordinates') and names the backing service (IGN Geoplateforme), so the operation and its scope are unambiguous. Nothing in the sibling list (aggregate_data, search_data, etc.) performs geocoding, so no disambiguation is required.

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?

Usage is implied by the statement that it converts French addresses/place names and returns coordinates, and the 'in France' constraint usefully bounds applicability. However, there is no explicit when-to-use framing, no statement about what to do when no match is found, and no pointer to any alternative for non-French or bulk lookups.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources