Weather Pro
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP transport | 3000 |
| MCP_TRANSPORT | No | Transport type: stdio or http | stdio |
| MCP_AUTH_TOKEN | No | Bearer token for HTTP transport authentication |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weatherA | Get current weather for a city. If the city name is ambiguous, asks you which one you meant. Optionally returns a what-to-wear tip. |
| compare_weatherA | Compare current weather across several cities. Streams progress as each city is fetched, and can be cancelled mid-flight. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan-my-day | Builds a day plan tailored to a city's current weather, with clothing, timing for outdoor activities, and precautions. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| weather-code-reference | Lookup table mapping WMO weather codes to descriptions |
TDQS
Scored across 2 tools
The two tools, get_weather and compare_weather, have clearly distinct purposes. get_weather focuses on a single city, while compare_weather handles multiple cities, so there is no ambiguity.
Both tools follow a consistent verb_noun pattern (compare_weather and get_weather) using snake_case. The naming is predictable and easy to parse.
With only 2 tools, the server is on the low end for a weather service, especially given the 'Pro' name. While the tools are useful, the count feels thin for comprehensive weather coverage.
The server covers current weather and comparison but lacks common operations like forecast or historical data. This is a notable gap for a weather-focused server.