Skip to main content
Glama

fr_address

Geocode and normalize French addresses via Base Adresse Nationale, returning normalized labels, postcodes, cities, INSEE codes, coordinates, and match scores; billed per successful x402 call.

Instructions

French address geocoding and normalisation via the official Base Adresse Nationale (api-adresse.data.gouv.fr). Returns normalised label, postcode, city, INSEE code, lat/lon and score. Costs 0.002 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": "fr_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesFree-text French address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses a per-call cost of 0.002 USDC on Base via x402 and the exact failure mode (a 402 challenge returned when no payment key is present). It does not cover rate limits, retry behavior, or what happens on unmatched addresses, keeping it short of a 5.

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?

Three tight sentences: purpose/source first, then the return payload, then the payment constraint. Every sentence contributes operational information with no restatement of the tool name.

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 one-parameter lookup with no output schema, the description supplies the returned fields (label, postcode, city, INSEE code, lat/lon, score) and the critical payment gate, which is enough to call it correctly. Minor gaps remain around error/empty-result handling and whether the charge applies to failed lookups.

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 single parameter q is already documented as a free-text French address, so the description adds no syntax or format guidance beyond the schema. Baseline 3 applies since the schema does the work.

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?

States a specific verb pair (geocoding and normalisation) and resource (French address) plus the upstream data source (Base Adresse Nationale / api-adresse.data.gouv.fr). The France-only scope implicitly separates it from eu_address and other siblings without needing to name them.

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 when to use it (free-text French addresses needing normalisation or lat/lon) and discloses the payment precondition, but never explicitly says when to prefer it over eu_address or fr_communes, nor what to do for non-French input.

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