OpenWeather-OneCall3-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENWEATHER_API_KEY | Yes | OpenWeather API key with One Call API 3.0 subscription |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_weatherA | Get current weather and forecast for a specific location (lat/lon). Returns current weather, daily forecast for 8 days, and hourly forecast for 48 hours. |
| get_weather_historyB | Get historical weather data for a specific timestamp (Time Machine). |
| get_coordinates_from_locationB | Retrieve latitude and longitude for a given city or administrative area name. Use this when you need coordinates (lat/lon) for a place. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct part of the weather API: current/forecast, historical time machine, and geocoding. There is no overlapping purpose, so an agent can easily select the right tool.
All three tools use a consistent get_ prefix with snake_case noun phrases. The pattern is predictable and readable across the set.
Three tools are well-scoped for a weather API wrapper, covering geocoding, current conditions with forecast, and historical data. Each tool earns its place without redundancy.
Core read operations are covered: geocoding, current/forecast, and historical weather. Minor gaps exist such as reverse geocoding, direct query by city name without a separate geocode step, or weather alerts/minutely data, but agents can work around these.