weather-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| contact | Yes | A contact URL or website identifying who is asking MET Norway. Required; there is no default, and the server refuses to start without it. | |
| home.lat | No | Optional home latitude, rounded to 2 decimals (about 1 km). Part of the optional [home] section. | |
| home.lon | No | Optional home longitude, rounded to 2 decimals (about 1 km). Part of the optional [home] section. | |
| home.name | No | Optional home place name to use when no place is given. Part of the optional [home] section. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
The weather in Norway, from MET Norway. Read each 'say' aloud as it is. No place means the owner's home.
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| weather_nowA | The weather right now. 'place' is a place in Norway as the owner said it, such as 'Bergen' or 'Moen i Agder'; omit it for home. Data from MET Norway and Kartverket. |
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
There is only one tool, so there is no possibility of confusing it with another. Its purpose (current weather for a Norwegian place) is clearly stated.
With a single tool, there is no convention to violate; 'weather_now' is lowercase snake_case and reads clearly. Consistency would only become an issue if more tools were added.
One tool is very thin for a weather server — the surface is a single query. It earns its place, but a lone tool makes the server borderline under-scoped rather than well-scoped.
Only current conditions are available; there is no forecast (hourly/daily), no historical data, and no way to resolve or search places beyond passing a free-text name. These are significant gaps that will cause agent failures for common weather requests like 'will it rain tomorrow?'.