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) |
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 ambiguity or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.
Since there is only one tool, it inherently follows a consistent pattern with itself. The naming uses a verb_noun format (get_alerts), which is clear and standard, and there are no other tools to introduce inconsistency.
A single tool is too few for a weather server, as it severely limits functionality. For a weather domain, agents would expect basic operations like getting current conditions, forecasts, or historical data, but this server only provides alerts for US states, making it incomplete and under-scoped.
The tool set is severely incomplete for a weather server. It only covers weather alerts for US states, missing core weather functionalities such as current weather, forecasts, or data for other regions. This creates significant gaps that will likely cause agent failures when broader weather queries are made.