geosphere-mcp-server
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_current_weatherA | Get current weather conditions for a location. |
| get_hourly_forecastA | Get an hour-by-hour weather forecast for a location. |
| get_storm_outlookA | Get the severe-weather outlook for a location: gusts and thunderstorms. |
| get_air_qualityA | Get air quality for a location: pollutants now and the AQI outlook. |
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 4 tools
Each tool targets a distinct weather aspect: current conditions, hourly forecast, storm outlook, and air quality. Even the current weather and hourly forecast have clear boundaries (present vs. future), and the storm outlook is specialized for severe weather with distinct outputs.
All tool names follow the same 'get_' prefix followed by a descriptive noun phrase, using snake_case consistently. There are no mixed conventions or vague verbs, making the naming pattern predictable and easy to infer for new tools.
Four tools is well-scoped for a specialized weather data server covering Austria and the Alpine region. Each tool provides a distinct and necessary data product without redundancy, and the count is within the ideal 3-15 range.
The tool surface covers the core needs of a weather data API: current conditions, short-term forecast, severe weather outlook, and air quality. A long-term (beyond 60 hour) forecast or historical data is missing, but such features are not clearly implied by the server's stated purpose of high-resolution data for the Alpine region.