Skip to main content
Glama
cmer81

Open-Meteo MCP Server

by cmer81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Geocoding

geocoding
Read-onlyIdempotent

Convert place names or postal codes into precise latitude and longitude coordinates and location details for weather data tools.

Instructions

Search for locations worldwide by place name or postal code. Returns geographic coordinates (latitude and longitude) and detailed location information. Use this tool when you need to convert a location name (e.g., "Paris", "New York") into precise coordinates (latitude/longitude) that are required by other tools. This is essential when you have a location name but need coordinates for data fetching tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPlace name or postal code to search for.
countNoMaximum number of results.
formatNojson
languageNoLanguage of the returned place names (e.g. "fr"); default English.
countryCodeNoOnly return places in this country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.5.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / count / description
      Previous value: -"Number of search results to return (maximum 100)"New value: +"Maximum number of results."
    • changedInput schema / properties / countryCode / description
      Previous value: -"ISO-3166-1 alpha2 country code to filter results (e.g., \"FR\", \"DE\", \"US\"). Limits search to a specific country."New value: +"Only return places in this country."
    • removedInput schema / properties / format / description
      Removed value: -"Return format for results"
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "json",
-  "protobuf"
-]New value: +[
+  "json"
+]
    • changedInput schema / properties / language / description
      Previous value: -"Language code for translated results (e.g., \"fr\", \"en\", \"de\"). Returns translated results if available, otherwise in English or native language."New value: +"Language of the returned place names (e.g. \"fr\"); default English."
    • changedInput schema / properties / name / description
      Previous value: -"Place name or postal code to search for. Minimum 2 characters required. Examples: \"Paris\", \"Berlin\", \"75001\", \"10967\""New value: +"Place name or postal code to search for."
  2. First observedv1.1.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds genuinely new information: worldwide scope, postal-code support, and the shape of the return value. It omits rate limits, auth requirements, and result-volume behavior, but goes well beyond restating the annotations.

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?

Three short sentences, front-loaded with the verb and the returned data. The final sentence largely repeats the preceding one ('when you have a location name but need coordinates'), which is mild redundancy but not damaging.

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?

Without an output schema the description carries the return-value burden and does so at a summary level (lat/long plus detailed location info). For a 5-parameter, mostly-documented read tool whose annotations cover safety, that is nearly complete; only return details and pagination/count behavior are left implicit.

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 80%, so the schema already explains name, count, language and countryCode; the description only restates the name/postal-code input. It adds no syntax or formatting guidance for the undocumented 'format' enum, so 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?

States a specific verb and resource (search for locations by place name or postal code) and names the output (coordinates plus detailed location info). This makes it immediately distinguishable from all weather/forecast siblings without opening any schema.

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?

Explicitly says when to use it: 'when you need to convert a location name ... into precise coordinates ... required by other tools,' and ties it to the data-fetching workflow. It gives no explicit exclusions or alternatives, but the upstream role is unmistakable.

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

Deploy Server

Other Tools