MCP Weather Project
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_alertsB | Get weather alerts for a US state. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| greet_user | Generate a greeting prompt |
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. The single tool 'get_alerts' has a clear and distinct purpose that cannot be confused with any other tool in this set.
The naming pattern is trivially consistent as there is only one tool. The tool name 'get_alerts' follows a clear verb_noun convention (get + alerts), which would be consistent if more tools were added.
A single tool is generally too few for a weather server's apparent scope, which typically includes forecasts, current conditions, and other weather data beyond just alerts. This feels thin and limited for the domain.
The tool surface is severely incomplete for a weather domain. It only provides alerts for US states, missing essential operations like getting forecasts, current weather, radar data, or international coverage, which will cause significant agent failures.