Weather MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENWEATHERMAP_API_KEY | Yes | Your API key from OpenWeatherMap |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weatherA | Get current weather for a city. Chinese city names are automatically translated to English. |
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 misselection. The single tool's purpose is unambiguous: retrieving current weather for a city.
The lone name get_weather follows a clear verb_noun convention. With only one tool there are no inconsistent patterns to compare against.
A single tool is thin even for a narrowly scoped weather server. A reasonable weather surface would typically include at least a forecast or multi-day lookup alongside current conditions.
The domain of weather naturally includes forecasts, hourly data, and historical lookups, none of which are present. Only current conditions are covered, leaving significant gaps an agent would hit quickly.