weather-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_alertsA | Get weather alerts for a US state. |
| get_forecastB | Get weather forecast for a location. |
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_alerts retrieves weather alerts for US states, while get_forecast provides forecasts for geographic coordinates. There is no overlap in functionality or ambiguity between them.
Both tools follow a consistent verb_noun naming pattern (get_alerts, get_forecast) with identical verb usage and snake_case formatting. The naming is perfectly predictable and uniform.
With only two tools, the server feels under-scoped for a weather domain. Essential operations like current conditions, historical data, or multi-location forecasts are missing, making the toolset thin and incomplete for typical weather-related tasks.
The toolset has significant gaps for a weather server. It lacks core functionalities such as current weather conditions, historical data, radar imagery, or air quality, and the forecast tool is limited to a single location without options for time ranges or units.