Skip to main content
Glama

eu_address

Geocode and normalise free-text addresses for France, Netherlands, Spain, and Switzerland using official national services, returning standardised labels, coordinates, and match scores.

Instructions

Address geocoding and normalisation through official national open services: France (Base Adresse Nationale), Netherlands (PDOK/BAG), Spain (CartoCiudad/IGN), Switzerland (swisstopo). Returns normalised label, street, number, postcode, city, region, coordinates 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": {
      "address": "<address>",
      "country": "<country>"
    },
    "name": "eu_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-10
addressYesFree-text address
countryYesFR, NL, ES or CH

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/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 the commercial model (0.002 USDC on Base per successful call, x402), the failure mode (402 challenge without a payment key), and the authoritative data sources. It stops short of stating error behaviour for unsupported countries or partial/no-match results, which an agent would want to know.

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

Conciseness4/5

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

Front-loaded with purpose and sources, then return fields, then payment terms – a sensible order with no filler. The third sentence compresses two distinct facts (price and 402 behaviour) but remains readable.

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?

No output schema exists, yet the description enumerates the returned fields, and the payment precondition is disclosed, which are the two riskiest unknowns for this tool. Minor gaps remain around failure/no-match behaviour and how a payment key is obtained.

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%, so the schema already documents address, country and limit. The description echoes the country set but adds nothing about address format expectations or what the limit string '1-10' does to results, so baseline 3 applies.

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?

States a specific verb pair (geocoding and normalisation) plus the exact upstream sources per country, and the description enumerates the return fields. It is clearly distinguishable from generic siblings, though it never addresses its overlap with fr_address, which appears to cover France already.

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 supported-country list implicitly tells the agent when the tool applies (FR, NL, ES, CH) and the payment note tells it what happens without a key. There is no explicit guidance on when to prefer this over fr_address for French addresses, or what to do for other countries.

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