Skip to main content
Glama
Sign In

Geo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Geocode

geocode
Read-onlyIdempotent

Convert an address or place name to up to 5 matching coordinates via OpenStreetMap Nominatim. Returns latitude, longitude, display_name, and place type for each result.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "1600 Pennsylvania Avenue, Washington DC"
    },
    "name": "geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesAddress or place name to geocode

Output Schema

NameRequiredDescriptionDefault
resultsYesList of geocoding results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "1600 Pennsylvania Avenue, Washington DC"
+  },
+  {
+    "query": "Eiffel Tower, Paris"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "description": "List of geocoding results",
+      "items": {
+        "properties": {
+          "display_name": {
+            "description": "Formatted address or place name",
+            "type": "string"
+          },
+          "latitude": {
+            "description": "Latitude coordinate",
+            "type": "number"
+          },
+          "longitude": {
+            "description": "Longitude coordinate",
+            "type": "number"
+          },
+          "type": {
+            "description": "OSM type of result",
+            "type": "string"
+          }
+        },
+        "required": [
+          "latitude",
+          "longitude",
+          "display_name",
+          "type"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "query": "1600 Pennsylvania Avenue, Washington DC"
-  },
-  {
-    "query": "Eiffel Tower, Paris"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "results": {
-      "description": "List of geocoding results",
-      "items": {
-        "properties": {
-          "display_name": {
-            "description": "Formatted address or place name",
-            "type": "string"
-          },
-          "latitude": {
-            "description": "Latitude coordinate",
-            "type": "number"
-          },
-          "longitude": {
-            "description": "Longitude coordinate",
-            "type": "number"
-          },
-          "type": {
-            "description": "OSM type of result",
-            "type": "string"
-          }
-        },
-        "required": [
-          "latitude",
-          "longitude",
-          "display_name",
-          "type"
-        ],
-        "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": "List of geocoding results",
+      "items": {
+        "properties": {
+          "display_name": {
+            "description": "Formatted address or place name",
+            "type": "string"
+          },
+          "latitude": {
+            "description": "Latitude coordinate",
+            "type": "number"
+          },
+          "longitude": {
+            "description": "Longitude coordinate",
+            "type": "number"
+          },
+          "type": {
+            "description": "OSM type of result",
+            "type": "string"
+          }
+        },
+        "required": [
+          "latitude",
+          "longitude",
+          "display_name",
+          "type"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "1600 Pennsylvania Avenue, Washington DC"
+  },
+  {
+    "query": "Eiffel Tower, Paris"
+  }
+]
  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 read-only, idempotent, and non-destructive properties. The description adds useful behavioral context: the external service (Nominatim), a result limit of up to 5, and the specific return fields. This goes beyond the annotation baseline without contradicting it.

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?

Two concise sentences, front-loaded with the core action, followed by constraints and return fields. Every word earns its place, with no fluff.

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 single-parameter read-only tool, the description covers purpose, data source, result limit, and return shape. Combined with the existing output schema and annotations, it leaves no significant gaps.

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 fully documents the single query parameter with an identical description, so schema coverage is 100%. The description reinforces the input type but adds no new semantic meaning beyond what the schema already provides.

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?

Clearly states the tool converts an address or place name to up to 5 matching coordinates, specifying the data source (OpenStreetMap Nominatim). This distinguishes it from reverse_geocode and other siblings.

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 when to use it: when you have an address or place name and need coordinates. It doesn't explicitly name alternatives like reverse_geocode, but the context is unmistakable.

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

All Geo 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