Skip to main content
Glama
slettmayer

geosphere-mcp-server

by slettmayer

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_current_weatherA

Get current weather conditions for a location.

High-resolution GeoSphere Austria data (AROME/INCA/nowcast). Serves Austria
and the Alpine region only; a point outside that grid returns an
out-of-coverage notice. The response states which datasets served it.

Args:
    latitude: Decimal latitude (e.g. 48.2208 for Vienna). Geocode city
        names to coordinates yourself.
    longitude: Decimal longitude (e.g. 16.3738 for Vienna).
get_hourly_forecastA

Get an hour-by-hour weather forecast for a location.

High-resolution GeoSphere AROME data (up to ~60 h, with C-LAEF
precipitation probability). Serves Austria and the Alpine region only; a
point outside that grid returns an out-of-coverage notice.

Args:
    latitude: Decimal latitude (e.g. 48.2208 for Vienna). Geocode city
        names to coordinates yourself.
    longitude: Decimal longitude (e.g. 16.3738 for Vienna).
    hours: Number of forecast hours (default 24, clamped to 1–60).
    start: Optional ISO 8601 start time (e.g. "2026-07-22T15:00"); the
        forecast begins at/after this instant instead of now.
get_storm_outlookA

Get the severe-weather outlook for a location: gusts and thunderstorms.

Reports the peak wind gust within the next hour and the next 12 hours,
whether a thunderstorm is expected within the next hour, when the next
thunderstorm is expected across the whole forecast horizon, and the peak
CAPE over the next 12 hours. Deliberately reports no severity verdict —
what counts as dangerous is the caller's judgement.

High-resolution GeoSphere AROME data, whose CAPE is gated by convective
inhibition. Serves Austria and the Alpine region only; a point outside that
grid returns an out-of-coverage notice.

The thunderstorm scan covers the AROME horizon, nominally ~60 h but shorter
when a run is stale or truncated. A "none in the next N h" answer names the
horizon it actually covered; it is not an all-clear beyond that.

Horizons round up to whole hours: the "next hour" window covers the hour
already under way plus the next one. A thunderstorm timestamp at or before
the current time means one is already in progress.

Args:
    latitude: Decimal latitude (e.g. 48.2208 for Vienna). Geocode city
        names to coordinates yourself.
    longitude: Decimal longitude (e.g. 16.3738 for Vienna).
get_air_qualityA

Get air quality for a location: pollutants now and the AQI outlook.

Reports current NO₂, O₃, PM10 and PM2.5 surface concentrations plus the
European Air Quality Index (1-6 EEA bands) for today, tomorrow and in two
days.

GeoSphere's WRF-Chem forecast (3 km) serves Austria and the Alpine region
only; a point outside that grid returns an out-of-coverage notice. These
are model forecasts, not station measurements.

An in-coverage point can still come back empty when a WRF-Chem run is
stale or incomplete — the response then says so and names the source that
drew the blank, which is a different answer from being out of coverage.

Args:
    latitude: Decimal latitude (e.g. 48.2208 for Vienna). Geocode city
        names to coordinates yourself.
    longitude: Decimal longitude (e.g. 16.3738 for Vienna).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.7/5.0

Scored across 4 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityActive
ResponsivenessNo issues