Weather MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENWEATHER_API_KEY | Yes | Your OpenWeatherMap API key for fetching weather data |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weatherC | Get current weather for a city |
| send_notificationB | Send a macOS notification with provided weather data |
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 2 tools
The two tools have clearly distinct purposes: get_weather retrieves weather data, while send_notification handles macOS notifications. There is no overlap in functionality, making it easy for an agent to choose the right tool for each task.
Both tools follow a consistent verb_noun naming pattern (get_weather and send_notification). The verbs are descriptive and appropriate for their actions, and there are no deviations in style or convention.
With only two tools, the server feels thin for a weather domain. It lacks essential operations like forecasting, historical data, or multi-location queries, which are typical for weather services. The scope is too limited for practical agent use.
The tool surface is severely incomplete for a weather server. It only provides current weather retrieval and notification sending, missing core features like forecasts, alerts, or location-based searches. This will likely cause agent failures when handling common weather-related requests.