Skip to main content
Glama

nominatim

by io.github.pipeworx-io
OverviewAdmin

Search Address

search_address
Read-onlyIdempotent

Search for coordinates of an address or place name. Returns latitude, longitude, display name, and place type for matched locations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Defaults to 5, max 50.
queryYesFree-form address or place name to search for (e.g. "Eiffel Tower, Paris").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYesArray of matched locations

Schema Changelog

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

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "description": "Array of matched locations",
+      "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. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "Eiffel Tower, Paris"
+  },
+  {
+    "limit": 10,
+    "query": "1600 Pennsylvania Avenue, Washington DC"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe read-only nature is fully disclosed. The description adds that it returns specific fields, but since an output schema exists, this is somewhat redundant. It does not mention any rate limits, data limitations, or other behavioral constraints, but with annotations present, the additional burden is minimal.

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 a single sentence of 18 words, front-loaded with the action 'Search' and immediately specifying the input and output. Every word contributes to understanding the tool's purpose. There is no fluff or redundancy.

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 simple two-parameter read-only tool with full schema descriptions, examples, and comprehensive annotations, the description is sufficient. It clearly conveys the core function and output. It does not explicitly mention the alternative reverse_geocode, but the sibling naming and tool name make this implicit, and the return fields are already documented in the output schema, so no critical context 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 input schema provides complete descriptions for both parameters: 'query' (free-form address or place name) and 'limit' (maximum results, default 5, max 50). The tool description does not add any parameter-specific details beyond what the schema already states, so schema coverage is 100% and the description adds no extra value in this dimension.

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 identifies the tool as a forward geocoder: 'Search for coordinates of an address or place name.' It specifies the resource (coordinates for an address/place name) and lists the return fields (latitude, longitude, display name, place type). This distinguishes it from the sibling 'reverse_geocode' tool, which does the opposite.

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 provides clear context: use this tool when you have an address or place name and need coordinates. It does not explicitly mention when not to use it or name alternative tools, but the sibling list includes 'reverse_geocode,' and the phrasing implies this is for forward geocoding. This is clear context without explicit exclusions.

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