Skip to main content
Glama

nominatim

by io.github.pipeworx-io
OverviewAdmin

Reverse Geocode

reverse_geocode
Read-onlyIdempotent

Convert latitude/longitude coordinates to a human-readable address. Returns nearest address, place name, and administrative boundaries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude in decimal degrees (e.g. 48.8584).
lonYesLongitude in decimal degrees (e.g. 2.2945).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude in decimal degrees
lonYesLongitude in decimal degrees
typeYesPlace type (e.g., landmark, city, road)
osm_idYesOpenStreetMap object ID
addressNoAddress components as key-value pairs
osm_typeYesOpenStreetMap object type (node, way, relation)
place_idYesUnique place identifier
importanceYesImportance score of the place
display_nameYesHuman-readable address or place name

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "lat": 48.8584,
+    "lon": 2.2945
+  },
+  {
+    "lat": 40.7128,
+    "lon": -74.006
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "address": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Address components as key-value pairs",
+      "type": "object"
+    },
+    "display_name": {
+      "description": "Human-readable address or place name",
+      "type": "string"
+    },
+    "importance": {
+      "description": "Importance score of the place",
+      "type": "number"
+    },
+    "lat": {
+      "description": "Latitude in decimal degrees",
+      "type": "number"
+    },
+    "lon": {
+      "description": "Longitude in decimal degrees",
+      "type": "number"
+    },
+    "osm_id": {
+      "description": "OpenStreetMap object ID",
+      "type": "number"
+    },
+    "osm_type": {
+      "description": "OpenStreetMap object type (node, way, relation)",
+      "type": "string"
+    },
+    "place_id": {
+      "description": "Unique place identifier",
+      "type": "number"
+    },
+    "type": {
+      "description": "Place type (e.g., landmark, city, road)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "place_id",
+    "osm_type",
+    "osm_id",
+    "lat",
+    "lon",
+    "display_name",
+    "type",
+    "importance"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "lat": 48.8584,
-    "lon": 2.2945
-  },
-  {
-    "lat": 40.7128,
-    "lon": -74.006
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "address": {
-      "additionalProperties": {
-        "type": "string"
-      },
-      "description": "Address components as key-value pairs",
-      "type": "object"
-    },
-    "display_name": {
-      "description": "Human-readable address or place name",
-      "type": "string"
-    },
-    "importance": {
-      "description": "Importance score of the place",
-      "type": "number"
-    },
-    "lat": {
-      "description": "Latitude in decimal degrees",
-      "type": "number"
-    },
-    "lon": {
-      "description": "Longitude in decimal degrees",
-      "type": "number"
-    },
-    "osm_id": {
-      "description": "OpenStreetMap object ID",
-      "type": "number"
-    },
-    "osm_type": {
-      "description": "OpenStreetMap object type (node, way, relation)",
-      "type": "string"
-    },
-    "place_id": {
-      "description": "Unique place identifier",
-      "type": "number"
-    },
-    "type": {
-      "description": "Place type (e.g., landmark, city, road)",
-      "type": "string"
-    }
-  },
-  "required": [
-    "place_id",
-    "osm_type",
-    "osm_id",
-    "lat",
-    "lon",
-    "display_name",
-    "type",
-    "importance"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "address": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Address components as key-value pairs",
+      "type": "object"
+    },
+    "display_name": {
+      "description": "Human-readable address or place name",
+      "type": "string"
+    },
+    "importance": {
+      "description": "Importance score of the place",
+      "type": "number"
+    },
+    "lat": {
+      "description": "Latitude in decimal degrees",
+      "type": "number"
+    },
+    "lon": {
+      "description": "Longitude in decimal degrees",
+      "type": "number"
+    },
+    "osm_id": {
+      "description": "OpenStreetMap object ID",
+      "type": "number"
+    },
+    "osm_type": {
+      "description": "OpenStreetMap object type (node, way, relation)",
+      "type": "string"
+    },
+    "place_id": {
+      "description": "Unique place identifier",
+      "type": "number"
+    },
+    "type": {
+      "description": "Place type (e.g., landmark, city, road)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "place_id",
+    "osm_type",
+    "osm_id",
+    "lat",
+    "lon",
+    "display_name",
+    "type",
+    "importance"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "lat": 48.8584,
+    "lon": 2.2945
+  },
+  {
+    "lat": 40.7128,
+    "lon": -74.006
+  }
+]
  5. 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 readOnly, idempotent, openWorld, and non-destructive behavior. The description adds context by stating the return value includes the nearest address, place name, and administrative boundaries. This provides useful behavioral detail beyond the annotations, though it does not cover error cases or edge conditions.

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, front-loaded with the primary purpose, and every clause adds value. It avoids redundancy with the schema and annotations.

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?

The tool is simple with two well-documented parameters, a clear output schema, and annotations covering safety and repeatability. The description sufficiently conveys the tool's purpose and expected results without increasing complexity.

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?

The input schema covers 100% of the parameter descriptions, including examples and units for lat/lon. The description does not add further parameter-level meaning, so the baseline score of 3 is appropriate.

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 precisely states the tool's function: converting lat/lon coordinates to a human-readable address. It distinguishes itself from sibling tools like search_address by explicitly mentioning the direction of conversion (coordinates to address) and the specific outputs (address, place name, administrative boundaries).

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 clearly implies usage when coordinates are available and an address is needed, but it does not explicitly discuss when not to use this tool or mention alternatives. The context is clear enough for an agent to infer appropriate usage.

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

All nominatim toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources