mcp-weather-tutorial
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 |
|---|---|
| geocode_cityA | Find the latitude and longitude of a city by name. Returns candidate matches, since city names are ambiguous -- there are Portlands in both Oregon and Maine. Use this before get_forecast, which only accepts coordinates. Args: name: City name to search for, e.g. "Denver" or "Paris". limit: Maximum number of candidate matches to return. |
| get_forecastA | Get the daily weather forecast for a set of coordinates. This tool does not accept city names. To look up a city, call geocode_city first and pass its latitude and longitude here. Args: latitude: Degrees north, e.g. 39.74 for Denver. longitude: Degrees east, e.g. -104.98 for Denver. days: How many days ahead to forecast, 1 to 16. |
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 2 tools
The two tools have completely distinct purposes: one converts city names to coordinates, the other retrieves forecasts from coordinates. There is no functional overlap.
Both tools follow the same verb_noun snake_case pattern (geocode_city, get_forecast), making them predictable and easy to understand.
With only 2 tools, the server feels minimal, but as a tutorial it is appropriately scoped for the basic workflow of converting a city name to coordinates then getting a forecast.
The server only provides geocoding and daily forecasts, omitting common weather features like current conditions, hourly forecasts, alerts, or historical data. This is notably incomplete for a general weather domain.