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. Args: state: Two-letter US state code (e.g. CA, NY) |
| get_forecastC | Get weather forecast for a location. Args: latitude: Latitude of the location longitude: Longitude of the 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 weather 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 across the tool set.
With only 2 tools for a weather server, the surface feels thin and incomplete for the domain. A weather service typically requires more operations (e.g., current conditions, historical data, multiple forecast types) to be useful for agents.
There are significant gaps in coverage for a weather domain. Missing essential operations like current weather conditions, historical data, air quality, or radar information. The two tools alone do not provide a complete weather service surface.