Skip to main content
Glama

nordic-data

by io.github.Mnymann
OverviewDiscussionsAdmin

autocomplete_address

Read-onlyIdempotent

Address autocomplete with coordinates. Sources: DAWA (DK, official address register), Kartverket/Geonorge (NO, official), BAN (FR, official Base Adresse Nationale), and OpenStreetMap Nominatim (SE, FI). Returns ranked address suggestions with lat/lng and a match confidence. Supports 5 countries: DK, NO, SE, FI, FR.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesPartial address — street name, postcode, city, or any combination. Min 2 characters.
countryYesISO 3166-1 alpha-2 country code, lowercase. Only dk, no, se, fi and fr are supported.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsNoRanked address candidates, best match first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO 3166-1 alpha-2 country code, lowercase."New value: +"ISO 3166-1 alpha-2 country code, lowercase. Only dk, no, se, fi and fr are supported."
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "dk",
-  "no",
-  "se",
-  "fi",
-  "ie",
-  "uk",
-  "fr",
-  "de",
-  "cz",
-  "pl",
-  "lv",
-  "ee",
-  "nl",
-  "be",
-  "lu"
-]New value: +[
+  "dk",
+  "no",
+  "se",
+  "fi",
+  "fr"
+]
    • changedOutput schema / properties / results / items / properties / source / description
      Previous value: -"DAWA / Kartverket / BAN / MML / Nominatim."New value: +"DAWA / Geonorge / BAN / Nominatim."
  2. Changed2 schema fields changed
    • addedOutput schema / properties / results
      Added value: +{
+  "description": "Ranked address candidates, best match first.",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "city": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "confidence": {
+        "description": "Match confidence 0-1.",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "coordinates": {
+        "additionalProperties": true,
+        "description": "WGS-84 {lat, lng}.",
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "displayName": {
+        "description": "Formatted address suitable for display.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "number": {
+        "description": "House number.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "postalCode": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "source": {
+        "description": "DAWA / Kartverket / BAN / MML / Nominatim.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "street": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}
    • removedOutput schema / properties / suggestions
      Removed value: -{
-  "description": "Ranked address candidates, best match first.",
-  "items": {
-    "additionalProperties": true,
-    "properties": {
-      "city": {
-        "type": "string"
-      },
-      "country": {
-        "description": "ISO 3166-1 alpha-2 code.",
-        "type": "string"
-      },
-      "house_number": {
-        "type": "string"
-      },
-      "lat": {
-        "description": "Latitude (WGS-84).",
-        "type": "number"
-      },
-      "lon": {
-        "description": "Longitude (WGS-84).",
-        "type": "number"
-      },
-      "postcode": {
-        "type": "string"
-      },
-      "source": {
-        "description": "DAWA / Kartverket / BAN / MML / Nominatim.",
-        "type": "string"
-      },
-      "street": {
-        "type": "string"
-      },
-      "text": {
-        "description": "Formatted address suitable for display.",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds valuable context beyond annotations: the specific official sources (DAWA, Kartverket, BAN, Nominatim) and the output structure (ranked suggestions with lat/lng and confidence). This enriches the agent's understanding without contradiction.

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 two sentences with no wasted words. It front-loads the core purpose ('Address autocomplete with coordinates'), then lists sources and return details efficiently. Every sentence earns its place.

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

Completeness5/5

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

Given the presence of an output schema (which covers return values), the description sufficiently covers purpose, sources, supported countries, and output highlights. Nothing critical is missing for an agent to call this tool correctly. The tool is simple and the description is complete.

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 both parameters (query and country) have clear descriptions in the schema. The tool description reiterates the supported countries but adds no new parameter-specific semantics beyond what the schema already provides. Baseline 3 is appropriate given full coverage.

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 a specific verb (autocomplete) and resource (addresses), and explicitly lists the data sources and supported countries. It is unambiguous and distinct from any sibling tool, none of which handle address autocomplete.

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

Usage Guidelines4/5

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

The description makes it clear this is the tool for address autocomplete in DK, NO, SE, FI, and FR, and that it returns ranked suggestions with coordinates. It does not explicitly mention alternatives, but no sibling tool competes for this use case, so the context is sufficient without exclusions.

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

All nordic-data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources