Skip to main content
Glama

nominatim

by io.github.pipeworx-io
OverviewAdmin

Lookup

lookup
Read-onlyIdempotent

Get details for OpenStreetMap locations by ID (e.g., "N123456" for node, "W654321" for way, "R111" for relation). Returns coordinates, names, and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesComma-separated list of OSM IDs with type prefix (e.g. "N123456,W654321"). N=node, W=way, R=relation.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYesArray of looked-up OSM objects

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: +[
+  {
+    "ids": "N123456,W654321"
+  },
+  {
+    "ids": "R111"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "description": "Array of looked-up OSM objects",
+      "items": {
+        "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"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "ids": "N123456,W654321"
-  },
-  {
-    "ids": "R111"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "results": {
-      "description": "Array of looked-up OSM objects",
-      "items": {
-        "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"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "results"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "description": "Array of looked-up OSM objects",
+      "items": {
+        "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"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "ids": "N123456,W654321"
+  },
+  {
+    "ids": "R111"
+  }
+]
  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 establish read-only, idempotent, and non-destructive behavior, so the description's burden is lower. It adds context by specifying the return content (coordinates, names, metadata) and clarifying the ID format. This is useful beyond the annotations and shows no 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, front-loaded with the action, and contains zero filler. Each clause contributes either the purpose, the ID format, or the output expectations.

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?

For a simple lookup tool with one well-documented parameter, strong annotations, and an output schema, the description is fully sufficient. It covers input format and scope, and the output schema handles return-value details. Nothing important is missing.

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 schema covers the single 'ids' parameter thoroughly with an explanation and examples, achieving 100% coverage. The description doesn't add significant parameter-level meaning beyond the schema—it mostly restates the format. Baseline 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 uses a specific verb and resource: 'Get details for OpenStreetMap locations by ID', with clear examples of N/W/R prefixes. This clearly distinguishes it from sibling tools like reverse_geocode or search_address, which operate on different input types.

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 the intended use case: when you have OSM IDs and need their details. It provides examples of valid ID formats, making the input expectations explicit. However, it does not explicitly mention alternatives or when not to use this tool, so it stops short of a 5.

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