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 has a distinct role: current conditions, air quality, general hourly forecasts, or specialized severe-weather diagnostics. Although the forecast tools share underlying data and overlapping time windows, their outputs and intended uses are clearly differentiated.
All four tools use consistent snake_case names with the same get_ prefix. The remaining name components clearly identify the weather product being retrieved.
Four tools are appropriate for this tightly scoped Austria and Alpine weather service. Each addresses a meaningful workflow without adding redundant or overly granular operations.
The set covers current weather, short-range hourly forecasting, severe-weather outlooks, and air quality, which supports the core read-only workflows well. Coordinate-only location inputs require external geocoding, and there is no longer-range or daily forecast summary, but these are minor limitations that agents can work around.