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_alertsC | Get weather alerts for US state Args: state: Two letter US state code (e.g CA, NY etc) |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently follows a consistent naming pattern. The tool name 'get_alerts' uses a clear verb_noun format, which would be consistent if more tools were added.
A single tool is too few for a weather server, as it lacks basic operations like getting current conditions, forecasts, or historical data. This severely limits the server's utility and scope.
The tool set is severely incomplete for a weather domain. It only provides alerts for US states, missing essential functions such as retrieving current weather, forecasts, or data for locations outside the US, making it inadequate for typical weather-related tasks.