Skip to main content
Glama
Sign In
open-meteo-mcp-server

open-meteo-mcp-server

by windsornguyen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

elevation

Get elevation data for any location by providing latitude and longitude coordinates using digital elevation models.

Instructions

Get elevation data for given coordinates using digital elevation models.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "elevation"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYesLatitude in WGS84 coordinate system
longitudeYesLongitude in WGS84 coordinate system

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states what the tool does, not any behavioral traits such as data sources, accuracy, rate limits, or return format. This is insufficient for a tool with no structured behavioral hints.

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?

A single sentence that is efficient and front-loaded. No extraneous words. Every part earns its place.

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?

With two simple parameters and no output schema, the description is mostly complete. However, it could mention the unit of elevation (e.g., meters) or the resolution of the model. Despite this minor gap, it adequately serves its purpose.

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 descriptive parameter descriptions (latitude/longitude in WGS84 with bounds). The tool description adds 'using digital elevation models' but does not enhance parameter understanding beyond the schema. 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?

The description clearly states the tool's action (Get elevation data) and the resource (given coordinates using digital elevation models). It effectively distinguishes from sibling tools that are weather-focused, though sibling differentiation is implicit.

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?

No explicit guidance on when to use this tool versus alternatives. While the sibling tools are weather-related, the description does not state exclusions or context. Usage is implied from the name and description but not explicit.

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