Open Meteo

Geocode

geocode

Read-onlyIdempotent

"What are the coordinates of [city]" / "lat lng for [place]" / "find [town] location" — resolve a place name (city, village, region) to lat/lng so the other Open-Meteo tools can use them. Free, keyless, multilingual; returns up to 100 matches ranked by population. Use before forecast / historical / air_quality / marine / flood when you only have a place name.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Place name (any language)
`count`	No	Max results, 1-100 (default 10)
`language`	No	ISO-639 lang for returned names (default en)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	No	List of geocoding results
`generationtime_ms`	No	API response generation time in milliseconds

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "name": "New York"
+  },
+  {
+    "count": 5,
+    "language": "fr",
+    "name": "Paris"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "generationtime_ms": {
+      "description": "API response generation time in milliseconds",
+      "type": "number"
+    },
+    "results": {
+      "description": "List of geocoding results",
+      "items": {
+        "properties": {
+          "admin1": {
+            "description": "First-order administrative division",
+            "type": "string"
+          },
+          "country": {
+            "description": "Country name in requested language",
+            "type": "string"
+          },
+          "country_code": {
+            "description": "ISO 3166-1 alpha-2 country code",
+            "type": "string"
+          },
+          "elevation": {
+            "description": "Elevation in meters",
+            "type": "number"
+          },
+          "feature_code": {
+            "description": "Geographic feature classification code",
+            "type": "string"
+          },
+          "id": {
+            "description": "Unique identifier for this location",
+            "type": "integer"
+          },
+          "latitude": {
+            "description": "Geographic latitude",
+            "type": "number"
+          },
+          "longitude": {
+            "description": "Geographic longitude",
+            "type": "number"
+          },
+          "name": {
+            "description": "Place name in requested language",
+            "type": "string"
+          },
+          "population": {
+            "description": "Population of the location",
+            "type": "integer"
+          },
+          "timezone": {
+            "description": "IANA timezone string",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds that the tool is free and keyless (no authentication needed), and returns up to 100 matches ranked by population. This provides useful behavioral context beyond annotations 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. The first sentence provides examples and the core action; the second adds constraints and usage guidance. It is front-loaded and efficient.

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 tool has 3 parameters with full schema coverage and an output schema, the description is complete. It explains purpose, usage, output behavior (ranking by population), and integration with sibling tools. No gaps remain.

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%, so baseline is 3. The description mentions the 'name' parameter implicitly via examples but does not add detail for 'count' or 'language'. The description adds minimal semantic value beyond the schema, so a 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 clearly states the tool resolves place names to lat/lng coordinates for use with other Open-Meteo tools. It provides example queries and explicitly distinguishes from sibling tools like forecast and historical. The verb 'resolve' and resource 'place name' are specific and unambiguous.

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

Usage Guidelines5/5

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

The description explicitly says to use this tool before forecast/historical/air_quality/marine/flood when only a place name is available, implying when not to use. It also notes it's free, keyless, and multilingual, giving context for when it's appropriate.

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

All Open Meteo tools Inspect

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.