Skip to main content
Glama

Open Meteo Geocode

open_meteo_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.

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": {
      "name": "New York"
    },
    "name": "open_meteo_geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPlace name (any language)
countNoMax results, 1-100 (default 10)
languageNoISO-639 lang for returned names (default en)

Output Schema

NameRequiredDescriptionDefault
resultsNoList of geocoding results
generationtime_msNoAPI response generation time in milliseconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered; the description adds genuinely new facts - free, keyless (no auth setup), multilingual, and results ranked by population up to 100. What it does not state is error behavior for ambiguous or unmatched names or any rate-limit/usage terms, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is essentially two dense lines: the example query phrasings first, then the scope-and-ordering sentence. The query phrasings are slightly verbose but earn their place as routing cues for informal requests; nothing is redundant with the title.

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?

With an output schema present, return values need not be explained, and the description still covers cost (free), auth (keyless), result limits (100), ordering (by population), and where the tool fits in the call sequence. For a 3-parameter geocoder this leaves no material gap for an agent to call it correctly.

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 coverage is 100% with inline descriptions for name, count (1-100, default 10) and language, so the baseline is 3. The description's 'multilingual' and 'up to 100 matches ranked by population' lightly reinforce the language and count parameters and add ranking context, but do not contribute new syntax or semantics beyond the schema.

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 names a specific verb and resource - 'resolve a place name (city, village, region) to lat/lng' - and frames it with real user phrasings ('What are the coordinates of [city]', 'lat lng for [place]'). It explicitly states the output is meant to feed 'the other Open-Meteo tools', so an agent can place it relative to the forecast/historical family immediately.

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?

Gives an explicit ordering rule: 'Use before forecast / historical / air_quality / marine / flood when you only have a place name.' That names the alternative tools and the precise condition (you have a name, not coordinates), which is exactly the decision an agent needs to make.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.