Skip to main content
Glama
cmer81

Open-Meteo MCP Server

by cmer81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Elevation

elevation
Read-onlyIdempotent

Get terrain height above sea level for one or many coordinate pairs, supporting batch latitude and longitude arrays in a single call.

Instructions

Get elevation data for given coordinates using digital elevation models. Supports batch lookups: pass arrays of the same length for latitude and longitude to query multiple points in one call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYes
longitudeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv2.5.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / latitude / anyOf
      Added value: +[
+  {
+    "maximum": 90,
+    "minimum": -90,
+    "type": "number"
+  },
+  {
+    "items": {
+      "maximum": 90,
+      "minimum": -90,
+      "type": "number"
+    },
+    "type": "array"
+  }
+]
    • removedInput schema / properties / latitude / description
      Removed value: -"Latitude in WGS84 coordinate system"
    • removedInput schema / properties / latitude / maximum
      Removed value: -90
    • removedInput schema / properties / latitude / minimum
      Removed value: --90
    • removedInput schema / properties / latitude / type
      Removed value: -"number"
    • addedInput schema / properties / longitude / anyOf
      Added value: +[
+  {
+    "maximum": 180,
+    "minimum": -180,
+    "type": "number"
+  },
+  {
+    "items": {
+      "maximum": 180,
+      "minimum": -180,
+      "type": "number"
+    },
+    "type": "array"
+  }
+]
    • removedInput schema / properties / longitude / description
      Removed value: -"Longitude in WGS84 coordinate system"
    • removedInput schema / properties / longitude / maximum
      Removed value: -180
    • removedInput schema / properties / longitude / minimum
      Removed value: --180
    • removedInput schema / properties / longitude / type
      Removed value: -"number"
  2. First observedv1.1.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, covering the safety profile. The description usefully adds the batch-query behavior and the equal-length array constraint, but omits units (meters?), coordinate datum, data source resolution, and accuracy expectations.

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 tight sentences, front-loaded with purpose before the batch detail. No filler or redundancy; every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 tool with annotations covering safety, this is mostly sufficient. It is missing the return shape (scalar vs. array of elevations) and units, which for an elevation lookup is a meaningful gap against no output schema.

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 0%, so the description carries the burden. It does explain the array form and the equal-length requirement for latitude/longitude, which justifies the anyOf schema. However, it adds nothing about units, decimal-degree format, or coordinate ordering, so it only partially compensates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (Get) and resource (elevation data for given coordinates) and notes the underlying method (digital elevation models), so the tool's function is unambiguous. It does not explicitly distinguish itself from the many weather siblings, though 'elevation' is self-evidently distinct from forecast tools.

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

Usage Guidelines3/5

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

The description explains how to use the parameters for batch lookups, which is genuine usage guidance, but it never states when to prefer this tool over alternatives or any prerequisites/exclusions. Usage is implied rather than framed as when/when-not.

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