french-admin-mcp

geocodage_inverse

Convert GPS coordinates to a complete French address. Retrieves street, city, and postal code using the National Address Database.

Instructions

Trouve l'adresse française correspondant à des coordonnées GPS (géocodage inverse). Retourne l'adresse complète, la commune, le code postal. Basé sur la Base Adresse Nationale (BAN).

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": {
      "longitude": "<longitude>",
      "latitude": "<latitude>"
    },
    "name": "geocodage_inverse"
  }
}

Input Schema

Name	Required	Description	Default
`longitude`	Yes	Longitude (ex : 2.3088 pour Paris)
`latitude`	Yes	Latitude (ex : 48.8534 pour Paris)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Jun 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns the full address, commune, and postal code, based on the Base Adresse Nationale. However, it does not mention any limitations, error handling, data freshness, or potential rate limits, leaving some behavioral gaps.

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 a single sentence that efficiently conveys the purpose, input, and data source, with no extraneous words. It is well-structured and front-loaded with the key action.

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?

Given the tool's simplicity (2 required parameters, no output schema), the description adequately explains what the tool does and what it returns. It covers the essential aspects such as the data source (BAN) and the returned fields (address, commune, postal code). However, it could optionally mention coordinate format or error handling for completeness, but it is sufficient for most use cases.

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 clear parameter descriptions (e.g., 'Longitude (ex : 2.3088 pour Paris)'). The tool description adds no additional semantic value beyond what the schema already provides, so the baseline score of 3 applies without enhancement.

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 verb 'Trouve' (finds) and the resource 'l'adresse française correspondant à des coordonnées GPS' (reverse geocoding). It specifies the exact functionality, which is distinct from all sibling tools that focus on administrative or simulation tasks.

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 usage for converting GPS coordinates to French addresses but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites. Since no sibling tool performs similar functions, the context is clear, but guidance is minimal.

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